Chrome uses almost 4x CPU vs. Safari on ad age page |
||||||||
Issue descriptionChrome Version: 60.0.3091.0 OS: macOS 10.12 What steps will reproduce the problem? (1) Visit this ad age page (site archived at https://drive.google.com/open?id=0BwcLL5PHtZQHVXA4am5lLTZKUkU ) What is the expected result? Chrome and Safari should consume roughly the same amount of CPU. What happens instead? Safari's renderer uses 16.3% CPU while the browser/renderer/GPU combo 60.5% CPU (+270%). This page is idle except for a boxed "+" control about 4/5 down the right edge of the page. It appears that this box causes the scroller tray to redraw itself at 60fps (per Quartz Debug and Chrome tracing). Safari also redraws this same area, but with much less CPU (note that Safari and Chrome's WindowServer usage is almost equal, so it's not a matter of Sarai unloading some work onto the WS). Specific CPU utilizations: Browser - 7.0% Renderer - 37.0% GPU - 16.5% IPC from 60fps animation costs around 4% in the browser process (e.g. see activity on the apple.com home page). I guess it's just surprising to me that it takes over 50% of a core to update the sliver of scroller tray.
,
May 25 2017
I'm not seeing repaint on linux, except for the hidden side panels that appear to repaint for a while (and overlap the scroll bar). It may be that the original report was not seeing scroll bar updates but rather that side panel updating. But after a while there are no repaints. Leaving open in the event we have more time to look into this.
,
May 25 2017
Right - the updates were little slivers along the right edge of the page that seemed to be the scroller area but could also be slivers of hidden panels in that same area. How long did you leave it before the repaints stopped? I was working with the page for several minutes (taking samples, etc.) and never saw the repaints stop.
,
May 25 2017
I think it was opening then closing the hidden panel of news feed. Maybe they stop doing some update after you view the feed.
,
May 28 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 29 2018
Time to close this, I think. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by junov@chromium.org
, May 25 2017