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

Issue 646207 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Tracing - CPU usage field is insufficiently granular.

Project Member Reported by erikc...@chromium.org, Sep 13 2016

Issue description

It looks like CPU usage is calculated in 5ms intervals. This seems reasonable when the graph is zoomed out, but when zoomed in, I would expect that the CPU usage is recalculated to have finer granularity.

In this example, there's no CPU usage from 6444 to 6445 [whereas the pink bar has same height from 6440 to 6445 ms].
 
trace_trivial_scrolling_page.json.gz
5.1 MB Download
Screen Shot 2016-09-12 at 5.34.03 PM.png
48.6 KB View Download
Since this is a linear algorithm, I think we may be able to compute this is highest fine grain level by computing cpu usage at all the events's starting points.

Setting that aside, I think the cpu_time_metric should be able to reuse the code that construct the cpu usage track.
Cc: alexandermont@chromium.org
Components: -Platform>DevTools>Performance>Tracing Infra>Client>Perf
Based on the screenshot, it looks like you pulled this from chrome://tracing/ which is actually not a part of Chrome DevTools (which is external facing web developer tools).

I've re-assigned it to the infra-perf team who I believe own this tool.

Comment 4 by benhenry@google.com, Nov 22 2016

Components: -Infra>Client>Perf
Labels: Performance-Tracing
Charlie: can someone from your team takes over this? I think it would be great to unify the code that draw the cpu usage chart with the code that compute cpu_time metric.
Owner: charliea@chromium.org
Status: Assigned (was: Untriaged)
I'll grab it, but can't give any promises on when I'll actually be able to take a look at it.
Components: Speed>Tracing
Labels: -Performance-Tracing
Status: Fixed (was: Assigned)
Going to mark this as Fixed due to alexandermont@'s work on making this track dynamically sized.

Sign in to add a comment