Issue metadata
Sign in to add a comment
|
Regressions in rendering/system_health benchmarks due to disabling perfetto tracing backend |
||||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 12
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1545e78d640000
,
Sep 16
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/1545e78d640000 Revert "Reland "Enable Perfetto by default for all telemetry tests"" by oysteine@chromium.org https://chromium.googlesource.com/chromium/src/+/00bea4ec5efd575a09604b89fbf6123b14690fb6 0.9382 → 2.291 (+1.352) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Oct 4
,
Oct 4
,
Oct 4
,
Oct 4
Issue 883524 has been merged into this issue.
,
Oct 4
Issue 880455 has been merged into this issue.
,
Oct 4
Issue 880300 has been merged into this issue.
,
Oct 4
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 12