Issue metadata
Sign in to add a comment
|
22.7% regression in blink_perf.layout at 579910:579927 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 7
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16b3d558640000
,
Aug 10
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/16b3d558640000 Add memory metric to trace event to investigate omnibox performance by etienneb@chromium.org https://chromium.googlesource.com/chromium/src/+/e1b21dc79f36dc4c7ddcb9ce606b94751eedeeca 1520 → 1532 (+12.07) Roll clang 337439:338452. by rnk@google.com https://chromium.googlesource.com/chromium/src/+/cc14e55b5cd9359e09aa9b8aa8795b100031abfb 1529 → 1934 (+405.2) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Jan 11
Assigned, but no owner or component? Please find a component and/or owner |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 7