Issue metadata
Sign in to add a comment
|
1.7%-1.9% regression in memory.desktop at 591073:591215 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 19
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12594387640000
,
Sep 20
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12594387640000 Reland "Use GL_COMMANDS_ISSUED_CHROMIUM query for shared memory GpuMemoryBuffers" by sunnyps@chromium.org https://chromium.googlesource.com/chromium/src/+/80d0a681332ba4c48d10e11f17d833eea89758ce 4.899e+08 → 4.964e+08 (+6.464e+06) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: None
,
Oct 1
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/17c54fcce40000
,
Oct 1
I've reissued the pinpoint job since the other two bugs filed for similar regressions ( issue 886725 and issue 886641 ) weren't reproducible. https://pinpoint-dot-chromeperf.appspot.com/job/17c54fcce40000
,
Oct 2
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/17c54fcce40000 Reland "Use GL_COMMANDS_ISSUED_CHROMIUM query for shared memory GpuMemoryBuffers" by sunnyps@chromium.org https://chromium.googlesource.com/chromium/src/+/80d0a681332ba4c48d10e11f17d833eea89758ce 4.893e+08 → 4.964e+08 (+7.043e+06) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: None |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 19