Issue metadata
Sign in to add a comment
|
2.1%-13.4% regression in rendering.mobile/avg_surface_fps at 592497:592590 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 25
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/10b05e57640000
,
Sep 25
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/10b05e57640000
,
Sep 26
Kicking off a bisect on a wider range.
,
Sep 26
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/102ee3d0e40000
,
Sep 27
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/102ee3d0e40000 Telemetry: fix a SF stats collector bug by chiniforooshan@chromium.org https://chromium.googlesource.com/catapult/+/5f6da8a57db16291c01a894083137c294b3b4e5f 19.72 → No values Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Oct 15
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/13de34c6e40000
,
Oct 15
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/13de34c6e40000 Buildbucket says the build completed successfully, but Pinpoint can't find the isolate hash.
,
Oct 15
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16904882e40000
,
Oct 15
All regressions except thread_raster_cpu_time_per_frame are fixed. I started another pinpoint job for thread_raster_cpu_time_per_frame.
,
Oct 16
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/16904882e40000
,
Oct 16
Since pinpoint couldn't reproduce the regression, and also I noticed that the graph has a land-revert pattern (around 581613-581665 for land and 592535-592590 for revert, I'll mark as won't fix. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 25