github-actions[bot] commented on issue #40067:
URL: https://github.com/apache/beam/issues/40067#issuecomment-6727921770

   
     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: Sun Nov  8 22:07:56 2026, metric_value: 2522.29
   timestamp: Sun Nov  8 01:02:53 2026, metric_value: 2482.75
   timestamp: Sat Nov  7 22:09:59 2026, metric_value: 2597.58
   timestamp: Fri Nov  6 22:10:53 2026, metric_value: 2527.21
   timestamp: Thu Nov  5 22:06:56 2026, metric_value: 2342.24 <---- Anomaly
   timestamp: Wed Nov  4 22:19:20 2026, metric_value: 2965.53
   timestamp: Tue Nov  3 22:14:56 2026, metric_value: 3006.37
   timestamp: Mon Nov  2 22:14:02 2026, metric_value: 2953.75
   timestamp: Sun Nov  1 22:18:36 2026, metric_value: 2844.18
   timestamp: Sat Oct 31 22:12:47 2026, metric_value: 2944.71
   timestamp: Fri Oct 30 22:14:14 2026, metric_value: 2919.39
   timestamp: Thu Oct 29 22:19:48 2026, metric_value: 2909.97
   timestamp: Wed Oct 28 22:15:48 2026, metric_value: 2904.19
   timestamp: Wed Oct 28 21:13:49 2026, metric_value: 2991.12
   timestamp: Tue Oct 27 22:20:09 2026, metric_value: 3075.53
   
   ```


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