New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 682498 link

Starred by 2 users
Status: WontFix
Owner:
█ shrike@chromium.org
Last visit > 30 days ago
Closed: Jul 2017
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

PerformanceMonitor.AverageCPU.BrowserProcess appears elevated on macOS 10.12 [compared to macOS 10.11].

Project Member Reported by erikc...@chromium.org, Jan 19 2017 
https://uma.googleplex.com/timeline_v2/?sid=5691d51557813e8c031e87e248093739
https://uma.googleplex.com/timeline_v2/?sid=5041834f57d8ae8ff12c627a79599527

All the percentiles appear elevated. It's unclear whether this is because Chrome performs more poorly on macOS 10.12, or if macOS 10.12 itself performs worse.
Screen Shot 2017-01-18 at 5.10.18 PM.png
736 KB View Download
Screen Shot 2017-01-18 at 5.10.19 PM.png
226 KB View Download

Comment 1 by erikc...@chromium.org, Jan 19 2017 

We're also seeing a spike in PerformanceMonitor.HighCPU.BrowserProcess in 10.12: https://bugs.chromium.org/p/chromium/issues/detail?id=665201. This correlates with the results seen here: more users are passing the threshold CPU level that triggers HighCPU.

Comment 2 by tapted@chromium.org, Jan 24 2017

Labels: Performance
Status: Available (was: Untriaged)
[mac triage] should we merge into  Issue 665201 ?

(and do we consider these to be actionable? Do we need to just change thresholds?)

Comment 3 by benhenry@chromium.org, May 3 2017

Labels: -Performance Performance-Power

Comment 4 by shrike@chromium.org, May 15 2017

Cc: -shrike@chromium.org
Owner: shrike@chromium.org
Status: Assigned (was: Available)
This metric seems to have recovered: https://uma.googleplex.com/timeline_v2/?sid=b29142c48db7f9b6bd639c712ef9ec3c

10.12.5 was released on March 27, and very soon after the averageCPU began falling. It seems this was a bug in 10.12 that Apple fixed.

I want to keep this open to check the numbers again in the near future, but I suspect we will be able to wontfix it.
Screen Shot 2017-05-15 at 4.07.13 PM.png
270 KB View Download

Comment 5 by shrike@chromium.org, Jul 24 2017

Status: WontFix (was: Assigned)
This metric has recovered on its own.
►

Sign in to add a comment