You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Performance Regression or Improvement: sideinpts_python_batch_1gb_1kb_10workers_1000window_99key_percent_dict:runtime
#40005
Grafana shows the runtime is usually around 15 to 20 min, with some spikes. Near the alert there is one fast run around 13 to 14 mins then a couple of 30 min spikes, and recent points are back in the normal range
I also compared GHA runs: Test 8 got slower on 31 August, but the similar Test 7 (1% keys) did not jump the same day and container tag was still beam-master-20260817 around that time
It looks unstable or flaky rather than a real slowdown
The times are basically the same, so the container change doesn’t look like the cause here and with Grafana also looking noisy (usually ~15 to 20 min, with some spikes), I still think this is unstable load test variance rather than a real lasting regression
Activity
aIbrahiim commentedon Sep 11, 2026
I investigated side input dataflow batch runs around the alert and checked Grafana for (batch / python, from 20 August until now):
https://metrics.beam.apache.org/d/-E9aGlFGk/side-input-load-tests?orgId=1&from=1787173200000&to=now&viewPanel=9
Grafana shows the runtime is usually around 15 to 20 min, with some spikes. Near the alert there is one fast run around 13 to 14 mins then a couple of 30 min spikes, and recent points are back in the normal range
I also compared GHA runs: Test 8 got slower on 31 August, but the similar Test 7 (1% keys) did not jump the same day and container tag was still beam-master-20260817 around that time
It looks unstable or flaky rather than a real slowdown
tvalentyn commentedon Sep 22, 2026
We should try to get to the bottom of this. Do you repro the regression via A/B testing, for example by passing --sdk_harness_container_image ?
aIbrahiim commentedon Oct 2, 2026
@tvalentyn I ran the Side Input Test 8 twice with --sdk_container_image, same test, only the worker image changed
First with beam-master-20260817: ~1803s (~30 min)
https://github.com/apache/beam/actions/runs/36714011882
Then with beam-master-20260831: ~1766s (~29 min)
https://github.com/apache/beam/actions/runs/36838732957
The times are basically the same, so the container change doesn’t look like the cause here and with Grafana also looking noisy (usually ~15 to 20 min, with some spikes), I still think this is unstable load test variance rather than a real lasting regression