Status Update
Comments
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #2
Added 1 regressions to the group
Internal (Googlers-only) Reports:
- Chromium:
(Legacy)
Top 1 affected measurements in android-pixel6-pro-perf:
- blink_perf.accessibility/SerializeLocationChanges_sum/location-changes-scrolling.html
28.09%: 5.625 -> 7.205 ms
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #3
Added 1 regressions to the group
Internal (Googlers-only) Reports:
- Chromium:
(Legacy)
Top 1 affected measurements in android-pixel6-perf:
- blink_perf.accessibility/SerializeLocationChanges_sum/location-changes-scrolling-content-visibility-auto.html
29.54%: 5.759 -> 7.46 ms
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #4
Added 1 regressions to the group
Internal (Googlers-only) Reports:
- Chromium:
(Legacy)
Top 1 affected measurements in android-pixel6-perf:
- blink_perf.accessibility/BrowserAccessibilityManager::OnLocationChanges_sum/location-changes-scrolling-content-visibility-auto.html
28.37%: 2.182 -> 2.801 ms
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #5
ChromiumPerf/android-pixel6-perf/blink_perf.accessibility/SerializeLocationChanges_sum/location-changes-scrolling-content-visibility-auto.html
Verification workflow id: projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/a570a4a8-7e2b-4e74-91e4-e8e0735b4064
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #6
reproduced the regression with statistic: {'control_median': 2.13383333305804, 'lower': 13.70603185807482, 'p_value': 3.725290298461914e-09, 'treatment_median': 2.456500000000233, 'upper': 18.43001637383388}.
Proceed to bisection.
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #7
Created by chromeperf@appspot.gserviceaccount.com
Benchmark: blink_perf.accessibility
Story: location-changes-scrolling-content-visibility-auto.html
Measurement: SerializeLocationChanges
The job has been scheduled on the "android-pixel6-perf" queue which currently has
1 pending jobs.
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #8
ChromiumPerf/android-pixel6-perf/blink_perf.accessibility/SerializeLocationChanges_sum/location-changes-scrolling-content-visibility-auto.html
To opt-out of further automatically started bisections for this issue, please
add the <b>Chromeperf-Auto-BisectOptOut</b> label.
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #10
12 revisions compared.
The top 3 are:
<b>1. [CodeHealth] Clean up the ContentCapture feature</b> by oksamyt@chromium.org
SerializeLocationChanges: 6.307 → 7.411 (+1.104) (+17.5%)
<b>2. Replace md5sum with devil_util</b> by martinkong@google.com
SerializeLocationChanges: 6.461 → 6.417 (-0.04334) (-0.6708%)
<b>3. Make NegotiateCodecs private to CodecVendor</b> by hta@webrtc.org
SerializeLocationChanges: 6.417 → 6.372 (-0.04511) (-0.7029%)
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.
al...@chromium.org <al...@chromium.org> #11
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #12
Created by oksamyt@google.com
Benchmark: blink_perf.accessibility
Story: location-changes-scrolling-content-visibility-auto.html
Measurement:
The job has been scheduled on the "android-pixel6-perf" queue which currently has
1 pending jobs.
ok...@chromium.org <ok...@chromium.org> #14
Re:
My CL (
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #15
Created by oksamyt@google.com
Benchmark: blink_perf.accessibility
Story: location-changes-scrolling-content-visibility-auto.html
Measurement:
The job has been scheduled on the "android-pixel6-perf" queue which currently has
1 pending jobs.
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #17
Created by oksamyt@google.com
Benchmark: blink_perf.accessibility
Story: location-changes-scrolling-content-visibility-auto.html
Measurement:
The job has been scheduled on the "android-pixel6-perf" queue which currently has
1 pending jobs.
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #19
ok...@chromium.org <ok...@chromium.org> #20
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #21
Created by oksamyt@google.com
Benchmark: blink_perf.accessibility
Story: location-changes-scrolling-content-visibility-auto.html
Measurement:
The job has been scheduled on the "android-pixel6-perf" queue which currently has
1 pending jobs.
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #23
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #24
Created by oksamyt@google.com
Benchmark: blink_perf.accessibility
Story: location-changes-scrolling-content-visibility-auto.html
Measurement:
The job has been scheduled on the "android-pixel6-perf" queue which currently has
1 pending jobs.
ok...@chromium.org <ok...@chromium.org> #26
@aleventhal, do you happen to know whether enabling content capture influences the speed of accessibility code? According to the pinpoint results (ContentCaptureTriggeringForExperiment
feature flag (which is enabled in the field trial testing config) seems to get rid of the regression, but it's not clear why.
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #27
al...@chromium.org <al...@chromium.org> #28
Hi Oksana, I never heard of ContentCapture before. Does it interact with the accessibility tree, layout or DOM? Are there some docs you can point me to? Feel free to ping me on chat/email
ok...@chromium.org <ok...@chromium.org> #29
Started an email thread with some more details.
Description
Internal (Googlers-only) Reports:
- Chromium:
(Legacy) Chromeperf Report:
Top 2 regressions (out of 2, with 0 improvements) in this group:
- ChromiumPerf/android-pixel-tangor-perf/blink_perf.accessibility/BrowserAccessibilityManager::OnLocationChanges_sum/location-changes-scrolling.html
27.50%: 2.5905 -> 3.303 ms
- ChromiumPerf/android-pixel-tangor-perf/blink_perf.accessibility/BrowserAccessibilityManager::OnAccessibilityEvents_sum/location-changes-scrolling.html
23.64%: 1.8445 -> 2.2805 ms
Top 2 affected measurements in android-pixel-tangor-perf:
- blink_perf.accessibility/BrowserAccessibilityManager::OnLocationChanges_sum/location-changes-scrolling.html
27.50%: 2.5905 -> 3.303 ms
- blink_perf.accessibility/BrowserAccessibilityManager::OnAccessibilityEvents_sum/location-changes-scrolling.html
23.64%: 1.8445 -> 2.2805 ms
Regressions grouped by blink_perf.accessibility includes data from the following benchmarks with listed owners:
blink_perf.accessibility: aleventhal@chromium.org
Commits in this range:
Chromium Git Hash:
Chromium Commit Position:
V8 Commit Position:
WebRTC Git Hash: