WAI
Status Update
No update yet.
Comments
ch...@appspot.gserviceaccount.com
Automatic regression verification started for measurement:
ChromiumPerf/win-10_laptop_low_end-perf/rendering.desktop/thread_total_rendering_cpu_time_per_frame/video_to_hw_accelerated_canvas
Verification workflow id: projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/5112c6d4-95b1-4ee6-bfd4-1e9406f744d4
ChromiumPerf/win-10_laptop_low_end-perf/rendering.desktop/thread_total_rendering_cpu_time_per_frame/video_to_hw_accelerated_canvas
Verification workflow id: projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/5112c6d4-95b1-4ee6-bfd4-1e9406f744d4
ch...@appspot.gserviceaccount.com
🥪 Regression verification projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/5112c6d4-95b1-4ee6-bfd4-1e9406f744d4 job 17e5aa03610000 for test: ChromiumPerf/win-10_laptop_low_end-perf/rendering.desktop/thread_total_rendering_cpu_time_per_frame/video_to_hw_accelerated_canvas
reproduced the regression with statistic: {'control_median': 45.221000000000004, 'lower': 54.54632812894196, 'p_value': 1.862645149230957e-09, 'treatment_median': 76.71385000000001, 'upper': 76.74048551703898}.
Proceed to bisection.
reproduced the regression with statistic: {'control_median': 45.221000000000004, 'lower': 54.54632812894196, 'p_value': 1.862645149230957e-09, 'treatment_median': 76.71385000000001, 'upper': 76.74048551703898}.
Proceed to bisection.
ch...@appspot.gserviceaccount.com
📍 Pinpoint job created and queued.
https://pinpoint-dot-chromeperf.appspot.com/job/17b5aa03610000
Created by chromeperf@appspot.gserviceaccount.com
Benchmark: rendering.desktop
Story: video_to_hw_accelerated_canvas
Measurement: thread_total_rendering_cpu_time_per_frame
The job has been scheduled on the "win-10_laptop_low_end-perf" queue which currently has
1 pending jobs.
Created by chromeperf@appspot.gserviceaccount.com
Benchmark: rendering.desktop
Story: video_to_hw_accelerated_canvas
Measurement: thread_total_rendering_cpu_time_per_frame
The job has been scheduled on the "win-10_laptop_low_end-perf" queue which currently has
1 pending jobs.
ch...@appspot.gserviceaccount.com
Automatic bisection started for measurement:
ChromiumPerf/win-10_laptop_low_end-perf/rendering.desktop/thread_total_rendering_cpu_time_per_frame/video_to_hw_accelerated_canvas
To opt-out of further automatically started bisections for this issue, please
add the <b>Chromeperf-Auto-BisectOptOut</b> label.
ChromiumPerf/win-10_laptop_low_end-perf/rendering.desktop/thread_total_rendering_cpu_time_per_frame/video_to_hw_accelerated_canvas
To opt-out of further automatically started bisections for this issue, please
add the <b>Chromeperf-Auto-BisectOptOut</b> label.
ch...@appspot.gserviceaccount.com
<b>📍 Found a significant difference at 1 commit.</b>
14 revisions compared.
https://pinpoint-dot-chromeperf.appspot.com/job/17b5aa03610000
<b>D3D11: Implement B2T using shaders.</b> by lehoangquyen@chromium.org
https://dawn.googlesource.com/dawn/+/95abcd95f5c14a33a1da109ad046353a676463ab
thread_total_rendering_cpu_time_per_frame: 46.51 → 80.46 (+33.95) (+73%)
Understanding performance regressions:
http://g.co/ChromePerformanceRegressions
Benchmark documentation link:
https://bit.ly/rendering-benchmarks
You can view the full results and re-run the Pinpoint job at:
https://pinpoint-dot-chromeperf.appspot.com/job/17b5aa03610000
If you think Pinpoint blamed the wrong commit, please add issue to
`Chromeperf-CulpritDetection-NeedsAttention` (hotlist:5670048) and
unassign yourself so that a sheriff can help diagnose.
14 revisions compared.
<b>D3D11: Implement B2T using shaders.</b> by lehoangquyen@chromium.org
thread_total_rendering_cpu_time_per_frame: 46.51 → 80.46 (+33.95) (+73%)
Understanding performance regressions:
Benchmark documentation link:
You can view the full results and re-run the Pinpoint job at:
If you think Pinpoint blamed the wrong commit, please add issue to
`Chromeperf-CulpritDetection-NeedsAttention` (hotlist:5670048) and
unassign yourself so that a sheriff can help diagnose.
le...@google.com
I think this is expected behavior.
- Before the patch, there were a lot of
dropped frames - After the patch, there were much
less dropped frames
Description
Internal (Googlers-only) Reports:
- Chromium:
(Legacy) Chromeperf Report:
Top 1 regressions (out of 1, with 0 improvements) in this group:
- ChromiumPerf/win-10_laptop_low_end-perf/rendering.desktop/thread_total_rendering_cpu_time_per_frame/video_to_hw_accelerated_canvas
60.87%: 47.829499999999996 -> 76.9448 unitless
Top 1 affected measurements in win-10_laptop_low_end-perf:
- rendering.desktop/thread_total_rendering_cpu_time_per_frame/video_to_hw_accelerated_canvas
60.87%: 47.829499999999996 -> 76.9448 unitless
Regressions grouped by rendering.desktop includes data from the following benchmarks with listed owners:
rendering.desktop: chrome-gpu-metrics@google.com, jonross@chromium.org
Commits in this range:
Chromium Commit Position:
V8 Commit Position:
WebRTC Git Hash: