New issue
Advanced search Search tips

Issue 874504 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature

Blocked on:
issue 859042
issue 852310
issue 852323
issue 855575
issue 855576
issue 856082
issue 862125
issue 862128
issue 862129



Sign in to add a comment

Investigate high task load in background tabs

Project Member Reported by altimin@chromium.org, Aug 15

Issue description

This is a tracking bug for all bugs filed based on high-load-in-background slow reports.
 
Blocking: 852323
Blocking: -852323
Blockedon: 852323
Blockedon: 856082
Status: Assigned (was: Untriaged)
Looks like something has regressed again here. Canary has jumped to 15% CPU usage in the 99th percentile: https://uma.googleplex.com/p/chrome/timeline_v2/?sid=40efa19e6f8a16675e4657aeef5d14f6
The interesting thing is that the total cpu time (as measured by RendererScheduler.TaskDurationPerThreadType) remained more or less the same.
Did something in the load metric change? The number of reported slow reports also stayed about the same.
It seems that the number of the samples has massively decreased (from 4 billion/day to 1 billion/day). I suspect that the number of active renderers has decreased, but I'm not quite sure why. It looks like proactive discarding, but it's not enabled on Android. It's something something OOPIF, I guess.

Comment 10 by eseckler@chromium.org, Yesterday (47 hours ago)

Cc: eseckler@chromium.org
Owner: ----
Status: Available (was: Assigned)
altimin@, is this still an issue?

Comment 11 by altimin@chromium.org, Yesterday (46 hours ago)

Given that nobody has done much work in the area, I believe that it is. However, I don't think that it's a priority for us right now.

Sign in to add a comment