Issue metadata
Sign in to add a comment
|
30.9%-66.1% regression in v8.browsing_mobile at 582919:583026 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 20
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16aa9281640000
,
Aug 22
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/16aa9281640000
,
Aug 23
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12bd52ee640000
,
Aug 23
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/159811b1640000
,
Aug 24
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/12bd52ee640000
,
Aug 24
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/159811b1640000 [heap] Use std::atomic for page flags. by hpayer@chromium.org https://chromium.googlesource.com/v8/v8/+/7f3f7e8a9547ece1a7f80ce902bc23632e902b0b 13.76 → 18.52 (+4.756) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Sep 26
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 20