Issue metadata
Sign in to add a comment
|
8.9% regression in rasterize_and_record_micro.top_25 at 578117:578214 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 27
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1382973ba40000
,
Jul 28
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/1382973ba40000 build: Enable ThinLTO in official Android builds. by pcc@google.com https://chromium.googlesource.com/chromium/src/+/1ba5d6113bd0b5342119bdf2d87946a827af1792 4.489 → 4.89 (+0.4017) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Jul 30
,
Aug 6
This seems to be another case similar to crbug.com/805582#c4 where a toolchain change caused a number of performance changes, the vast majority of which were improvements, but a few outliers were regressions. Perf reports (for my change and the two relands): https://chromeperf.appspot.com/group_report?rev=578195 https://chromeperf.appspot.com/group_report?rev=578854 https://chromeperf.appspot.com/group_report?rev=579308 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 27