Issue metadata
Sign in to add a comment
|
1%-6.6% regression in system_health.memory_mobile at 585103:585240 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 24
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/11f2aea6640000
,
Aug 27
,
Aug 27
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/112f3696640000
,
Aug 28
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/112f3696640000 Remove Modern flag and hardcode #isChromeModernDesignEnabled to true by twellington@chromium.org https://chromium.googlesource.com/chromium/src/+/5955e6d67f3799a0cdd9dba7df8fa5460499f99f 4.875e+07 → 5.048e+07 (+1.733e+06) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Aug 28
It looks like this is the same as issue 877247 , which similarly reported a gpu memory regression when Modern is enabled. miu@ - is it reasonable to mark this as a duplicate?
,
Aug 28
Also, the pinpoint job seems to specifically identify system_health.memory_mobile. I would be really surprised if the CL identified affected WebView performance since it was a visual redesign of Clank UI (code primary isolated to chrome/android/java). Are there other pinpoint jobs need to identify culprits for the other alerts in comment #1?
,
Aug 29
miu@ - the pinpoint job in #6 identified a gpu regression that's already covered in issue 877247 . Will you please confirm whether this bug can be closed or whether more work is needed to investigate the other alerts in the original bug report?
,
Oct 10
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 24