Performance Regression or Improvement: gbk_python_batch_load_test_2gb_of_100KB_records:runtime

Open
  • Is something wrong?
#40,643 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
performance, testing-qa

Research direction

The regression is in the Python GroupByKey load test gbk_python_batch_load_test_2gb_of_100KB_records, configured in .test-infra/jenkins/job_LoadTests_GBK_Python.groovy around line 83. Start with the Triage performance alert issues section of the analyzers README and the linked dashboard panel to check whether the 71.00 runtime on Oct 14 is real or noise. Done means the anomaly is either explained by a commit or closed as a false positive with the reasoning recorded.

Written by the indexing model from the issue text.

Description

awaiting triage perf-alert

Performance change found in the
test: gbk_python_batch_load_test_2gb_of_100KB_records for the metric: runtime.

For more information on how to triage the alerts, please look at
Triage performance alert issues section of the README.

Test description: GroupByKey Python Load test - 2GB of 100kB records
python | GBK | Large records (100kB)
Test Dashboard - http://metrics.beam.apache.org/d/UYZ-oJ3Zk/gbk-load-tests?orgId=1&var-processingType=batch&var-sdk=python&from=now-6M&to=now&viewPanel=4&inspect=4
Test link - https://github.com/apache/beam/blob/5e38decf9e723a385057131b01bbd33d8c60bda3/.test-infra/jenkins/job_LoadTests_GBK_Python.groovy#L83


timestamp: Fri Oct 16 16:51:21 2026, metric_value: 70.00
timestamp: Thu Oct 15 16:51:43 2026, metric_value: 84.00
timestamp: Wed Oct 14 16:49:57 2026, metric_value: 71.00 <---- Anomaly
timestamp: Tue Oct 13 17:11:03 2026, metric_value: 13.00
timestamp: Mon Oct 12 17:28:41 2026, metric_value: 38.00
timestamp: Sun Oct 11 17:22:48 2026, metric_value: 11.00
timestamp: Sat Oct 10 17:17:39 2026, metric_value: 14.00
timestamp: Fri Oct  9 17:24:03 2026, metric_value: 18.00
timestamp: Thu Oct  8 17:04:34 2026, metric_value: 80.00
timestamp: Wed Oct  7 17:01:44 2026, metric_value: 18.00
timestamp: Tue Oct  6 16:57:54 2026, metric_value: 107.00
timestamp: Mon Oct  5 17:06:36 2026, metric_value: 17.00
timestamp: Sun Oct  4 18:14:01 2026, metric_value: 47.00
Dominant language
Java
Stars
8.7k
Forks
4.8k
Avg merge
2d 9h
Merged PRs (30d)
368

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/beam

All issues in apache/beam

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.