Issue metadata
Sign in to add a comment
|
39.2% regression in v8.browsing_mobile at 568483:568607 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 9
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14a5fb0aa40000
,
Jul 9
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/14a5fb0aa40000 Buildbucket says the build completed successfully, but Pinpoint can't find the isolate hash.
,
Jul 12
,
Jul 13
Issue 862654 is fixed. I'm re-running these jobs.
,
Jul 13
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/10079511a40000
,
Jul 14
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/10079511a40000
,
Jul 16
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14c7c036a40000
,
Jul 16
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/14c7c036a40000 Set TouchStartExpectedSoon only after we seen a blocking event by chaopeng@chromium.org https://chromium.googlesource.com/chromium/src/+/4a2ebc8dad89ca0042d0babd619f4ea35e3ac072 2.707e+06 → 3.948e+06 (+1.241e+06) [embedded-builtins] Enable on all arches except x86 for benchmarks by sigurds@chromium.org https://chromium.googlesource.com/v8/v8/+/f5a8352b0fbba0d88104de7949a0d0c238765cf8 3.905e+06 → 3.688e+06 (-2.174e+05) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Jul 16
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 9