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

Issue 704010 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

15.4% regression in startup.cold.blank_page/window_display_time on cros-clapper at 30400000936800001:30400000936900000

Project Member Reported by deanliao@chromium.org, Mar 22 2017

Issue description

Performance dashboard identified a 15.4% regression in startup.cold.blank_page/window_display_time on cros-clapper at revision range 30400000936800001:30400000936900000. Graph: https://chromeperf.appspot.com/report?masters=ChromeOSPerf&bots=cros-clapper&tests=startup.cold.blank_page%2Fwindow_display_time&checked=window_display_time%2Cwindow_display_time_ref%2Cref&rev=30400000936900000

 

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

Owner: cywang@chromium.org
Start bisecting between 9368.0.0..9369.0.0.
Status: Assigned (was: Untriaged)
Explictly assigning. A CL you landed tripped one of the speed metrics we measure in the lab. If this is the first time this has happened to one of your CLs, or if it's been a while, please read: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/addressing_performance_regressions.md

We're looking for one of the following:
1. Justification via explanation
2. Plan to revert or fix
3. Angry rage throwing of equipment at my head

Just be aware that I'm trained in trumpet playing and First Aid and am not afraid to use it.

Note: This was a bulk edit message and not very personal.
Labels: -Performance-Sheriff
Components: OS>Performance

Sign in to add a comment