Issue metadata
Sign in to add a comment
|
1.5%-1.8% regression in system_health.memory_mobile at 580386:580423 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 8
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16e28994640000
,
Aug 10
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/16e28994640000 [scanner] Decode utf8 as chunks come in to utf16, allowing unbuffered streaming by verwaest@chromium.org https://chromium.googlesource.com/v8/v8/+/928e7b2973feb8a8b82b4405c29570553cc1d33b 2.926e+07 → 2.972e+07 (+4.599e+05) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Aug 20
,
Aug 24
My side of the regression was reverted and recovered, but it seems like the second graph didn't recover. Is that a different issue?
,
Aug 24
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12efae51640000
,
Aug 24
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12efae51640000 [scanner] Decode utf8 as chunks come in to utf16, allowing unbuffered streaming by verwaest@chromium.org https://chromium.googlesource.com/v8/v8/+/928e7b2973feb8a8b82b4405c29570553cc1d33b 2.927e+07 → 2.952e+07 (+2.545e+05) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Sep 17
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 8