github-actions[bot] opened a new issue, #40190:
URL: https://github.com/apache/beam/issues/40190

   
     Performance change found in the
     test: 
`gbk_python_batch_load_test_fanout_8_times_with_2GB_10byte_records_total` for 
the metric: `runtime`.
   
     For more information on how to triage the alerts, please look at
     `Triage performance alert issues` section of the 
[README](https://github.com/apache/beam/tree/master/sdks/python/apache_beam/testing/analyzers/README.md#triage-performance-alert-issues).
   
   
   `Test description:` GroupByKey Python Load test - fanout 8 times with 2GB 
10-byte records total
   python | GBK | Fanout 8
   Test Dashboard - 
http://metrics.beam.apache.org/d/UYZ-oJ3Zk/gbk-load-tests?orgId=1&var-processingType=batch&var-sdk=python&from=now-90d&to=now&viewPanel=6
   Test link - 
https://github.com/apache/beam/blob/5e38decf9e723a385057131b01bbd33d8c60bda3/.test-infra/jenkins/job_LoadTests_GBK_Python.groovy#L129
   
   
   ```
   
   timestamp: Sun Sep 20 17:31:38 2026, metric_value: 46.00
   timestamp: Sat Sep 19 17:22:47 2026, metric_value: 116.00
   timestamp: Fri Sep 18 17:45:15 2026, metric_value: 107.00 <---- Anomaly
   timestamp: Thu Sep 17 17:25:45 2026, metric_value: 37.00
   timestamp: Wed Sep 16 17:27:09 2026, metric_value: 39.00
   timestamp: Tue Sep 15 17:40:24 2026, metric_value: 57.00
   timestamp: Mon Sep 14 17:22:12 2026, metric_value: 90.00
   timestamp: Sun Sep 13 17:40:00 2026, metric_value: 56.00
   timestamp: Sat Sep 12 17:23:40 2026, metric_value: 59.00
   timestamp: Fri Sep 11 17:23:33 2026, metric_value: 54.00
   timestamp: Thu Sep 10 17:28:58 2026, metric_value: 56.00
   timestamp: Wed Sep  9 17:29:44 2026, metric_value: 60.00
   timestamp: Tue Sep  8 17:27:54 2026, metric_value: 61.00
   
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to