Skip to content

Performance Regression or Improvement: test_cloudml_benchmark_cirteo_no_shuffle_10GB-runtime_sec:runtime_sec  #38412

New issue
New issue
Closed
Closed
Performance Regression or Improvement: test_cloudml_benchmark_cirteo_no_shuffle_10GB-runtime_sec:runtime_sec #38412
Labels
awaiting triageperf-alertAutomatically filed performance-related alerts.
Milestone
2.77.0 Release

Description

@github-actions
github-actions
bot
opened on May 7, 2026

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.

Test description: TFT Criteo test on 10 GB data with no Reshuffle.
Test link - Test link


timestamp: Thu May  7 22:30:50 2026, metric_value: 2959.05
timestamp: Wed May  6 22:32:51 2026, metric_value: 2827.72
timestamp: Tue May  5 22:27:37 2026, metric_value: 2884.74 <---- Anomaly
timestamp: Mon May  4 22:23:27 2026, metric_value: 2313.99
timestamp: Sun May  3 22:18:02 2026, metric_value: 2220.72
timestamp: Sat May  2 22:11:48 2026, metric_value: 2217.29
timestamp: Fri May  1 22:20:21 2026, metric_value: 2338.62
timestamp: Thu Apr 30 22:20:19 2026, metric_value: 2219.75
timestamp: Thu Apr 30 00:58:51 2026, metric_value: 2309.95
timestamp: Tue Apr 28 22:28:09 2026, metric_value: 2283.32
timestamp: Mon Apr 27 22:32:10 2026, metric_value: 2391.52
timestamp: Sun Apr 26 22:17:56 2026, metric_value: 2379.47
timestamp: Sat Apr 25 22:14:38 2026, metric_value: 2423.89

Activity

  1. github-actions
    added
    awaiting triage
    perf-alertAutomatically filed performance-related alerts.
    on May 7, 2026
  2. damccorm
    removed
    awaiting triage
    on May 22, 2026

  3. github-actions commented on Aug 5, 2026

    @github-actions
    github-actionsBot
    on Aug 5, 2026 – with GitHub Actions
    ContributorAuthor

    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.

    Test description: TFT Criteo test on 10 GB data with no Reshuffle.
    Test link - Test link

    
timestamp: Wed Aug  5 22:34:27 2026, metric_value: 2951.01
timestamp: Tue Aug  4 22:35:26 2026, metric_value: 2840.13
timestamp: Mon Aug  3 22:51:13 2026, metric_value: 4266.28
timestamp: Sun Aug  2 22:22:11 2026, metric_value: 2788.16
timestamp: Sat Aug  1 22:24:18 2026, metric_value: 2748.90 <---- Anomaly
timestamp: Fri Jul 31 22:28:26 2026, metric_value: 2387.70
timestamp: Thu Jul 30 22:27:28 2026, metric_value: 2461.83
timestamp: Wed Jul 29 22:15:06 2026, metric_value: 2319.85
timestamp: Tue Jul 28 22:47:09 2026, metric_value: 3931.32
timestamp: Mon Jul 27 22:21:04 2026, metric_value: 2322.61
timestamp: Sun Jul 26 22:16:04 2026, metric_value: 2383.53
timestamp: Sat Jul 25 22:14:05 2026, metric_value: 2329.38
timestamp: Fri Jul 24 22:20:56 2026, metric_value: 2321.26
timestamp: Thu Jul 23 22:34:43 2026, metric_value: 2337.92
timestamp: Wed Jul 22 22:19:25 2026, metric_value: 2294.34
  4. github-actions
    added
    awaiting triage
    on Aug 5, 2026

  5. Amar3tto commented on Aug 31, 2026

    @Amar3tto
    Amar3tto
    on Aug 31, 2026
    Collaborator

    https://metrics.beam.apache.org/d/C9nj1oxVk/tft-criteo-benchmarks?orgId=1&from=now-90d&to=now&refresh=1d

  6. Amar3tto
    closed this as completedon Aug 31, 2026
  7. github-actions
    added this to the 2.77.0 Release milestone on Aug 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    awaiting triageperf-alertAutomatically filed performance-related alerts.

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions