Issue metadata
Sign in to add a comment
|
A zero-to-nonzero to 4% regression in rendering.mobile at 587661:587775 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 4
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/15dbdf5d640000
,
Sep 9
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/15dbdf5d640000 Use GL_COMMANDS_ISSUED_CHROMIUM query for shared memory GpuMemoryBuffers by sunnyps@chromium.org https://chromium.googlesource.com/chromium/src/+/370c8bc2082a3665ccc45fef39955fd550170b61 0.6581 → 4.083 (+3.425) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Sep 13
The above CL was reverted, and relanded with important fixes to fix incorrect rendering. Those fixes should also mitigate these regressions.
,
Sep 15
Thanks for taking a look. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 4