Issue metadata
Sign in to add a comment
|
3.5%-83.7% regression in rendering.mobile/tasks_per_frame_total_all at 601213:601297 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 25
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/141eb9cee40000
,
Oct 25
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/141eb9cee40000
,
Nov 20
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/166be5ebe40000
,
Nov 20
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/129c7700140000
,
Nov 20
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/166be5ebe40000 Remove input metric ukm sampling by nzolghadr@chromium.org https://chromium.googlesource.com/chromium/src/+/f509a32b60352f85ed29950b1a24752ad14ce35e tasks_per_frame_total_all: 37.8 → 40.29 (+2.486) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Nov 20
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/129c7700140000 Remove input metric ukm sampling by nzolghadr@chromium.org https://chromium.googlesource.com/chromium/src/+/f509a32b60352f85ed29950b1a24752ad14ce35e tasks_per_frame_total_all: 37.87 → 40.22 (+2.345) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Nov 21
nzolghadr@, the bisect points to your change, could you take a look?
,
Nov 21
Tim, do you think this is the effect of us reporting UKM for input metrics? Does that have that much overload?
,
Nov 21
It's possible. Might be worth an independent couple of perf tryjobs? |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 25