Issue metadata
Sign in to add a comment
|
22.5% regression in rendering.desktop at 583538:583588 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 20
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1049fc81640000
,
Aug 21
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/1049fc81640000 Enable Viz Display Compositor on perf bots by fsamuel@chromium.org https://chromium.googlesource.com/chromium/src/+/209e15b44e0c2c2d127b5c9a4416b996d663cc5e 10.27 → 12.31 (+2.044) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Aug 22
This is probably related to a BeginFrame perturbation issue.
,
Oct 23
Sounds like we should WontFix.
,
Oct 23
tasks_per_frame_ etc. should not be affected by begin-frame issues I think. Re-opening, and /cc+ nzolghadr@, sahel@ from the input-team; we have had a lot of regressions on input around that time. I wonder if this could be related to that.
,
Nov 15
Passing along to nzolghadr@ as I'm not actively looking at this at the moment. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 20