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

Issue 751570 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
brucedaw...@chromium.org
charliea@chromium.org
altimin@chromium.org
█ shrike@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Ensure that all top level tasks are traced

Project Member Reported by skyos...@chromium.org, Aug 2 2017 
According to findings from charliea@, not all top level tasks are currently being traced. We should

1) Instrument these tasks

2) Create a benchmark that ensures >NN% of top-level CPU activity is being instrumented

Example missing functions:

DoIdleWork > ActivateHighResolutionTimer
TimedWaitUntil > WaitForSingleObjectEx
TimedWaitUntil > TimeTicks::Now

Comment 1 by nedngu...@google.com, Aug 2 2017

Components: Speed>Benchmarks

Comment 2 by nedngu...@google.com, Aug 2 2017 

For 2), I suggest we use existing power/thread_times benchmarks instead of spin up new ones.

Comment 3 by tdres...@chromium.org, Aug 2 2017 

Yeah, I think we need a new metric, not necessarily a new benchmark.

How much infrastructure work is involved in gathering ETW data at the same time as the Chrome trace?

Comment 4 by vadimsh@chromium.org, Aug 2 2017

Components: -Infra>Platform>Scheduler
(wrong Scheduler)

Comment 5 by nedngu...@google.com, Aug 2 2017

Components: Speed>Metrics

Comment 6 by skyos...@chromium.org, Aug 4 2017

Components: Blink>Scheduling

Comment 7 by nedngu...@google.com, Aug 5 2017

Cc: shrike@chromium.org brucedaw...@chromium.org

Comment 8 by tdres...@chromium.org, Nov 22 2017 

In the short term, should we just address the missing functions we're currently aware of?

Comment 9 by charliea@chromium.org, Dec 5 2017 

SGTM

Comment 10 by dproy@chromium.org, Mar 15 2018

Labels: -Type-Bug Type-Feature
►

Sign in to add a comment