Issue metadata
Sign in to add a comment
|
3.6%-160.1% regression in v8.browsing_mobile at 580792:581349 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 20
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1032591a640000
,
Aug 25
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/1032591a640000 FMPDetector: Use network quiet signal from IdlenessDetector by ksakamoto@chromium.org https://chromium.googlesource.com/chromium/src/+/208565993af870c86cff06c27dbc67066694bf61 20.99 → 29.95 (+8.962) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Aug 27
My change affects renderer's scheduling policy (the scheduler may stay in the "loading" state longer), so it may have changed the GC timings. I think it's okay to WontFix this, considering the small number of affected benchmarks. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 20