New issue
Advanced search Search tips

Issue 721930 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
nzolghadr@chromium.org
dtapu...@chromium.org
tdres...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Feature



Sign in to add a comment

Optimize LatencyTracker::ComputeTouchAndWheelScrollLatencyHistograms

Project Member Reported by mfomitchev@chromium.org, May 12 2017 
It appears - LatencyTracker::ComputeTouchAndWheelScrollLatencyHistograms has a pretty significant cost, up to 5% total frame CPU time - see  issue 719549 . We should find out which parts are expensive and see if we can optimize them. Immediate suspects are string concatenations and UMA macros. If applicable, we should apply similar optimizations to other parts of LatencyTracker/RWHLatencyTracker.

Comment 1 by tdres...@chromium.org, May 15 2017

Cc: dtapu...@chromium.org nzolghadr@chromium.org
The other thing to do here is delete old histograms, which is on my plate.

Comment 2 by benhenry@chromium.org, May 17 2017

Components: Speed>Metrics
Labels: -Performance -Type-Bug Type-Feature

Comment 3 by tdres...@chromium.org, Oct 4 2017 

Mikhail, any plans to follow up on this?

Comment 4 by mfomitchev@chromium.org, Oct 4 2017 

No immediate plans - I am likely going to be focused on perf stuff that is blocking Viz/Mus launches in the near future. Please feel free to grab/reassign.

Comment 5 by tdres...@chromium.org, Oct 4 2017

Cc: mfomitchev@chromium.org
Labels: Hotlist-Input-Dev
Owner: ----
Marking available.

Comment 6 by mfomitchev@chromium.org, Nov 21 2017

Cc: -mfomitchev@chromium.org

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

Bug triage ping: no update in the last 100 days. 

Is there a more suitable owner for this bug?
►

Sign in to add a comment