Performance Regression or Improvement: test_cloudml_benchmark_criteo_10GB-runtime_sec:runtime_sec

未关闭
#41,089 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
python, tensorflow

调研方向

Start with the triage guidance in sdks/python/apache_beam/testing/analyzers/README.md and inspect the benchmark referenced in sdks/python/apache_beam/testing/benchmarks/cloudml/cloudml_benchmark_test.py. Compare the anomalous runtime with nearby measurements and investigate what changed in the benchmark or its execution environment. Done means the performance alert is explained and any confirmed regression has a clear resolution.

由索引模型根据 Issue 内容生成。

描述

awaiting triage perf-alert

Performance change found in the
test: test_cloudml_benchmark_criteo_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.
Test link - https://github.com/apache/beam/blob/42d0a6e3564d8b9c5d912428a6de18fb22a13ac1/sdks/python/apache_beam/testing/benchmarks/cloudml/cloudml_benchmark_test.py#LL104C7-L104C41


timestamp: Sun Nov  8 01:46:38 2026, metric_value: 2622.62
timestamp: Sat Nov  7 22:54:32 2026, metric_value: 2670.46
timestamp: Fri Nov  6 22:54:34 2026, metric_value: 2617.58
timestamp: Thu Nov  5 22:46:00 2026, metric_value: 2341.57 <---- Anomaly
timestamp: Wed Nov  4 23:08:40 2026, metric_value: 2956.38
timestamp: Tue Nov  3 23:04:19 2026, metric_value: 2959.26
timestamp: Mon Nov  2 23:03:59 2026, metric_value: 2993.29
timestamp: Sun Nov  1 23:07:41 2026, metric_value: 2942.03
timestamp: Sat Oct 31 23:00:36 2026, metric_value: 2865.71
timestamp: Fri Oct 30 23:04:56 2026, metric_value: 3040.11
timestamp: Thu Oct 29 23:09:40 2026, metric_value: 2988.82
timestamp: Wed Oct 28 23:11:51 2026, metric_value: 3360.26
timestamp: Wed Oct 28 22:05:18 2026, metric_value: 3085.76
timestamp: Tue Oct 27 23:09:30 2026, metric_value: 2958.39

主要语言
Java
星标
8.7k
派生
4.8k
平均合并
2 天 12 小时
30 天内合并 PR
371

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

apache/beam 的其他 Issue

查看 apache/beam 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。