pytorch - 💡(How to fix) Fix DISABLED vision_maskrcnn graph breaks (dynamic_cpu_max_autotune_inductor_amp_freezing_torchbench) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
pytorch/pytorch#181378Fetched 2026-04-25 06:02:41
View on GitHub
Comments
1
Participants
2
Timeline
39
Reactions
0
Timeline (top)
mentioned ×16subscribed ×16labeled ×6commented ×1

Root Cause

This benchmark was disabled because graph break count regressed in CI after PR #181360.

RAW_BUFFERClick to expand / collapse

Platforms: dynamo

This benchmark was disabled because graph break count regressed in CI after PR #181360.

vision_maskrcnn: graph_breaks=31, expected=30 (+1 regression, 5 unique break types unchanged)

CSV: benchmarks/dynamo/ci_expected_accuracy/dynamic_cpu_max_autotune_inductor_amp_freezing_torchbench_inference.csv

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @kadeng @amjames @Lucaskabela @jataylo @azahed98

extent analysis

TL;DR

The benchmark regression in graph break count may be resolved by investigating and addressing the cause of the additional graph break in the vision_maskrcnn model.

Guidance

  • Review the changes introduced in PR #181360 to identify potential causes of the graph break count regression.
  • Compare the current graph break count of 31 with the expected count of 30 to understand the nature of the regression.
  • Analyze the CSV file at benchmarks/dynamo/ci_expected_accuracy/dynamic_cpu_max_autotune_inductor_amp_freezing_torchbench_inference.csv for more detailed information on the benchmark results.
  • Investigate the 5 unique break types that remain unchanged to determine if they are related to the regression.

Notes

The exact cause of the regression is unclear, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Investigate and address the cause of the additional graph break in the vision_maskrcnn model, as it is likely the primary cause of the benchmark regression.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING