What problem does it solve?
Graph breaks occur when a model, pipeline, or script is split into more graphs than necessary during TT-XLA compilation, making logs noisy and debugging harder.
In TT-XLA, graph breaks often arise from tracing stages such as torchdynamo tracing, torch_xla tracing, or rare byproducts of torch.export, and are not simply different MLIR modules.
This guide helps you distinguish true graph breaks from expected graph variants and provides a structured approach to diagnosing and fixing the root causes.
Core Features & Use Cases
- Count and categorize MLIR module blocks per graph to quantify graph breaks.
- Map each graph to its source code path (torchdynamo, torch_xla, export) to identify responsible stage.
- Produce a prioritized action list with reproducible steps and optional patch scripts to fix the break.
Quick Start
Input the TT-XLA debug log and I will generate a graph-break analysis with root causes and fixes.