New issue
Advanced search Search tips

Issue 725231 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Chrome renderer spends 3x CPU vs. Safari on wired.com

Project Member Reported by shrike@chromium.org, May 22 2017

Issue description

Chrome Version: 60.0.3091.0
OS: macOS 10.12

What steps will reproduce the problem?
(1) Visit wired.com (site archived at https://drive.google.com/open?id=0BwcLL5PHtZQHcEk3VTBuWllNdVk )

What is the expected result?
Given that CPU use is confined to the renderer in both Chrome and Safari, the renderers/browsers should consume about the same amount of energy.

What happens instead?
Safari's renderer consumes 3.5% vs. Chromium at 10%, almost 2x greater.

Part of the extra CPU use comes from unneeded painting activity, which is covered under  Issue 725230 .

 

Comment 1 by junov@chromium.org, May 25 2017

Components: -Blink Blink>JavaScript
Looked at a trace. Most CPU work in the render process seems to be in V8.execute and MajorGC.  Assigning to JS component for further triage.

Comment 2 by jochen@chromium.org, May 26 2017

Owner: jarin@chromium.org
Status: Assigned (was: Untriaged)
assigning to current perf sherrif

Sign in to add a comment