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

   
     Performance change found in the
     test: `cogbk_python_batch_load_test_reiterate_4times_10KB_values` 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:` CoGroupByKey Python Load test - reiterate 4 times 10kB 
values
   python | coGBK | reiteration 10kB value
   Test Link - 
https://github.com/apache/beam/blob/5e38decf9e723a385057131b01bbd33d8c60bda3/.test-infra/jenkins/job_LoadTests_coGBK_Python.groovy#L96
   Test Dashboard - 
http://metrics.beam.apache.org/d/fK0U4JqWz/cogbk-load-tests?orgId=1&var-processingType=batch&var-sdk=python&viewPanel=4
   
   
   ```
   
   timestamp: Fri Sep 26 16:19:18 2025, metric_value: 139.00
   timestamp: Thu Sep 25 16:06:59 2025, metric_value: 131.00
   timestamp: Wed Sep 24 16:14:28 2025, metric_value: 414.00 <---- Anomaly
   timestamp: Tue Sep 23 16:14:42 2025, metric_value: 127.00
   timestamp: Mon Sep 22 16:07:26 2025, metric_value: 95.00
   timestamp: Sun Sep 21 16:05:19 2025, metric_value: 108.00
   timestamp: Sat Sep 20 16:03:11 2025, metric_value: 121.00
   timestamp: Fri Sep 19 16:10:48 2025, metric_value: 106.00
   timestamp: Thu Sep 18 16:14:30 2025, metric_value: 106.00
   timestamp: Wed Sep 17 16:28:43 2025, metric_value: 132.00
   timestamp: Tue Sep 16 16:23:43 2025, metric_value: 133.00
   timestamp: Mon Sep 15 16:28:43 2025, metric_value: 145.00
   timestamp: Sun Sep 14 16:07:47 2025, metric_value: 122.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