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

Issue 599697 link

Starred by 3 users
Status: Assigned
Owner:
sque@chromium.org
Cc:
kouhei@chromium.org
█ dhsharp@chromium.org
tzik@chromium.org
█ rapati@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
cwp



Sign in to add a comment

blink overhead increased from 2.4% to 3.4% over time during session restore

Project Member Reported by sque@chromium.org, Mar 31 2016 
Data obtained from CWP (go/cwp). See attached graph.

Blink overhead as a %age of CPU cycles during session restore on x86_64 previously hovered around 2.4% from M44 to M47. But starting with M48, its overhead has increased steadily over time to 3.4%.

Not sure what the overhead increase is due to. Will have to break it down by class within Blink and find out more.
blink on restore session.png
62.5 KB View Download

Comment 1 by tkent@chromium.org, Apr 4 2016

Cc: kouhei@chromium.org tzik@chromium.org

Comment 2 by kojii@chromium.org, Apr 6 2016

Components: -Blink Blink>Memory

Comment 3 by tkent@chromium.org, Apr 12 2016

Components: -Blink>Memory Blink
Remove unofficial Blink>Memory component.

Comment 4 by yosin@chromium.org, Apr 20 2016

Components: -Blink Blink>MemoryAllocator
►

Sign in to add a comment