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

   
     Performance change found in the
     test: `test_cloudml_benchmark_cirteo_no_shuffle_10GB-runtime_sec` for the 
metric: `runtime_sec`.
   
     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:` TFT Criteo test on 10 GB data with no Reshuffle.
   Test link - [Test 
link](https://github.com/apache/beam/blob/42d0a6e3564d8b9c5d912428a6de18fb22a13ac1/sdks/python/apache_beam/testing/benchmarks/cloudml/cloudml_benchmark_test.py#L82)
   
   
   ```
   
   timestamp: Sat Jun  7 22:01:21 2025, metric_value: 2307.03
   timestamp: Fri Jun  6 22:04:05 2025, metric_value: 2430.08
   timestamp: Thu Jun  5 22:05:27 2025, metric_value: 2396.73
   timestamp: Wed Jun  4 22:08:01 2025, metric_value: 2370.51
   timestamp: Tue Jun  3 22:03:43 2025, metric_value: 2437.46
   timestamp: Mon Jun  2 22:06:38 2025, metric_value: 2356.56 <---- Anomaly
   timestamp: Sun Jun  1 22:15:17 2025, metric_value: 2988.47
   timestamp: Sat May 31 22:16:44 2025, metric_value: 2937.92
   timestamp: Fri May 30 22:22:16 2025, metric_value: 3085.93
   timestamp: Thu May 29 22:19:19 2025, metric_value: 3128.36
   timestamp: Wed May 28 22:20:35 2025, metric_value: 3259.40
   timestamp: Tue May 27 22:19:34 2025, metric_value: 3241.35
   timestamp: Mon May 26 22:11:39 2025, metric_value: 3004.47
   timestamp: Sun May 25 22:12:59 2025, metric_value: 2977.77
   timestamp: Sat May 24 22:12:00 2025, metric_value: 2976.41
   timestamp: Fri May 23 22:13:22 2025, metric_value: 2978.97
   
   ```


-- 
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