Issue metadata
Sign in to add a comment
|
1.3%-2.4% regression in system_health.memory_mobile at 581889:581984 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 16
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12c05c56640000
,
Aug 17
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12c05c56640000 Revert "Reland "[SessionStorageS13N] Enabling mojo SessionStorage by default"" by dpranke@chromium.org https://chromium.googlesource.com/chromium/src/+/6ef5af6759c379b78b518789649b1e73e8e91a2a 3.773e+07 → 3.886e+07 (+1.136e+06) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Aug 27
@dmurph - this was your change, right? I think you resolved this one way or another?
,
Sep 11
Yes - I had to disable session storage until I can fix some crashers (where i'm basically onion souping). |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 16