# Test Case STR 1. Open the browser 2. Open the specified Gslide document (https://goo.gl/wn1ScS) 3. Wait for loading finished 4. Press "End" Key to the end page 5. Press "Enter" to create a new slide # Hardware OS: Windows 7 CPU: i7-3770 3.4GMhz Memory: 16GB Ram Hard Drive: 1TB SATA HDD Graphics: GK107 [GeForce GT 640]/ GF108 [GeForce GT 440/630] # Browsers Firefox version: 49.01 Chrome version: 53.0.2785.143m # Result Browser | Run time (median value) Firefox | 17,117 ms Chrome | 13,367 ms
Profiler data as below: https://cleopatra.io/#report=2f83ff4dcc56b74b71ad417441526f0ab5a499fc
2 years ago
platform-rel: --- → +
I looked at a profile for this. I ignored the page load and only considered the time taken to add a new slide to the end of the document. Chrome is noticeably faster to add a blank slide. We take about 200ms to add a new slide, and Chrome is near instantaneous. We're spending about 10% of that time doing reflow on SVG boxes, and the remaining time seems to be spent running interpreted JS.
WONTFIX for now to limit perf benchmark bugs to high impact. Please re-opened when new input latency metrics landed and confirm this issue.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.