New issue
Advanced search Search tips

Issue 773938 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

99.2% regression in speedometer/Total on cros-samus at 31880000985300000

Project Member Reported by bccheng@chromium.org, Oct 12 2017

Issue description

Speedometer regression across the board on R62. It went back to normal in R63.

Performance dashboard identified a 4.2% regression in speedometer/Total on cros-samus at revision range 32010000990400001:32030000990600000. Graph: https://chromeperf.appspot.com/report?masters=ChromeOSPerf&bots=cros-samus&tests=speedometer%2FTotal&checked=Total%2CTotal_ref%2Cref&rev=32030000990600000

 
Status: Started (was: Untriaged)
Bisecting... though 4.2% regression is challenging to bisector.
If you look at the chromeperf graph, the regression is more like 100% than 4%.
Bisecting... though 4.2% regression (CrOS version range: 62.9901.44.0 - 63.9906.0.0 ) is challenging to bisector.

I would bisect the CrOS version range: 62.9844.0.0 - 62.9853.0.0 as it has 100% regression.

Also, the regression was back between 63.9915.0.0-63.9917.0.0. I'll bisect to see which commit fix the issue.
Summary: 99.2% regression in speedometer/Total on cros-samus at 31880000985300000 (was: 4.2% regression in speedometer/Total on cros-samus at 32010000990400001:32030000990600000)
there is a ~4% degradation being tracked in  issue 773561 . My team is working on that.
Owner: cywang@chromium.org

Sign in to add a comment