Issue metadata
Sign in to add a comment
|
2.3% regression in system_health.memory_mobile at 592430:592483 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 20
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/11f313b8e40000
,
Sep 22
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/11f313b8e40000 Add tooltip for onscreen keyboard button in tray by zhelfins@chromium.org https://chromium.googlesource.com/chromium/src/+/2c5af88016d82f300cdd5ac4fbd0708df5496511 1.517e+07 → 1.526e+07 (+9.182e+04) Remove supressNextClick JavaScript. by michaeldo@chromium.org https://chromium.googlesource.com/chromium/src/+/cc7b9c6822f296b79bd26587379ee74120211bb6 1.522e+07 → 1.535e+07 (+1.293e+05) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/system-health-benchmarks
,
Oct 1
IIUC, this alert is about a performance change in the "Android Nexus6 WebView Perf" bot. My change titled "Remove supressNextClick JavaScript." only affects iOS, so assigning to zhelfins@ for investigation.
,
Oct 1
My change is exclusively within ChromeOS, reassigning to michaeldo to investigate.
,
Oct 1
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/11d63f34e40000
,
Oct 1
It looks like neither of these CLs should be the cause because they are not changes which affect Android. I've triggered a bisect according to instructions at http://g.co/ChromePerformanceRegressions, but (to me) it looks like this may be caused by a dip in the graph which then simply recovered to normal values based on the "all graphs" link in c#1.
,
Oct 1
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/11d63f34e40000 |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 20