Issue metadata
Sign in to add a comment
|
6%-637.1% regression in rendering.mobile/mean_frame_time_renderer_compositor at 598489:598650 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 11
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/10f40e32e40000
,
Oct 11
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/10f40e32e40000 gpu: Expand oopr workaround to fallback to ES2 to all android versions. by khushalsagar@chromium.org https://chromium.googlesource.com/chromium/src/+/332d9329983d602d6bc1f4e0b64afec2307e70ba queueing_durations: 0.2733 → 1.661 (+1.388) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Oct 11
This should have brought us back to the performance we had with GPU raster. I'm going to run the rendering benchmarks again now that OOP is also using ES2 and compare against GPU raster to see what the real regressions are.
,
Oct 13
,
Oct 16
,
Oct 16
Issue 895269 has been merged into this issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 11