This release is a pre-release and may not be stable for production use.
TritonParse
A comprehensive visualization and analysis tool for Triton kernel compilation and launch — helping developers analyze, debug, and understand Triton kernel compilation processes.
✨ Key Features
🔍 Visualization & Analysis
- 🚀 Launch Difference Analysis - Detect and visualize kernel launch parameter variations
- 📊 IR Code View - Side-by-side IR viewing with synchronized highlighting and line mapping
- 🔄 File Diff View - Compare kernels across different trace files side-by-side
- 📝 Multi-format IR Support - View TTGIR, TTIR, LLIR, PTX, and AMDGCN
- 🎯 Interactive Code Views - Click-to-highlight corresponding lines across IR stages
🔧 Reproducer & Debugging Tools
- 🔄 Standalone Script Generation - Extract any kernel into a self-contained Python script
- 💾 Tensor Data Reconstruction - Preserve actual tensor data or use statistical approximation
- 🎯 Custom Templates - Flexible reproducer templates for different workflows
- 🐛 Bug Isolation - Share reproducible test cases for debugging and collaboration
📊 Structured Logging & Analysis
- 📝 Compilation & Launch Tracing - Capture detailed events with source mapping
- 🔍 Stack Trace Integration - Full Python stack traces for debugging
- 📈 Metadata Extraction - Comprehensive kernel statistics
🛠️ Developer Tools
- 🌐 Browser-based Interface - No installation required, works in your browser
- 🔒 Privacy-first - All processing happens locally, no data uploaded
🚀 Quick Start
1. Installation
Four options to install:
# install nightly version
pip install -U --pre tritonparse
# install stable version
pip install tritonparse
# install from source
git clone https://github.com/meta-pytorch/tritonparse.git
cd tritonparse
pip install -e .
# pip install the latest version from github
pip install git+https://github.com/meta-pytorch/tritonparse.git
Prerequisites: Python ≥ 3.10, Triton ≥ 3.4.0, GPU required (NVIDIA/AMD)
TritonParse relies on new features in Triton. If you're using nightly PyTorch, Triton is already included. Otherwise, install the latest Triton:
pip install triton
2. Generate Traces
import tritonparse.structured_logging
import tritonparse.parse.utils
# Initialize logging with full tracing options
tritonparse.structured_logging.init(
"./logs/",
enable_trace_launch=True, # Capture kernel launch events (enables torch.compile tracing automatically)
enable_more_tensor_information=True, # Optional: collect tensor statistics (min/max/mean/std)
)
# Your Triton/PyTorch code here
# ... your kernels ...
# Parse and generate trace files
tritonparse.parse.utils.unified_parse("./logs/", out="./parsed_output")
💡 Note:
enable_trace_launch=Trueautomatically enables tracing for both native Triton kernels (@triton.jit) andtorch.compile/ TorchInductor kernels.
📝 Example output (click to expand)
================================================================================
📁 TRITONPARSE PARSING RESULTS
================================================================================
📂 Parsed files directory: /scratch/findhao/tritonparse/tests/parsed_output
📊 Total files generated: 2
📄 Generated files:
1. 📝 dedicated_log_triton_trace_findhao__mapped.ndjson.gz (7.2KB)
2. 📝 log_file_list.json (181B)
================================================================================
✅ Parsing completed successfully!
================================================================================
3. Visualize Results
Visit https://meta-pytorch.org/tritonparse/ and open your local trace files (.ndjson.gz format).
🔒 Privacy Note: Your trace files are processed entirely in your browser - nothing is uploaded to any server!
4. Generate Reproducers (Optional)
Extract any kernel into a standalone, executable Python script for debugging or testing:
# Generate reproducer for the first launch event
# (--line is 0-based: line 0 is compilation event, line 1 is first launch event)
tritonparseoss reproduce ./parsed_output/trace.ndjson.gz --line 1 --out-dir repro_output
# Run the generated reproducer
cd repro_output/<kernel_name>/
python repro_*.py
Python API:
from tritonparse.reproducer.orchestrator import reproduce
result = reproduce(
input_path="./parsed_output/trace.ndjson.gz",
line_index=0, # 0-based index (first event is 0)
out_dir="repro_output"
)
🎯 Common Reproducer Use Cases (click to expand)
- 🐛 Bug Isolation: Extract a failing kernel into a minimal standalone script
- ⚡ Performance Testing: Benchmark specific kernels without running the full application
- 🤝 Team Collaboration: Share reproducible test cases with colleagues or in bug reports
- 📊 Regression Testing: Compare kernel behavior and performance across different versions
- 🔍 Deep Debugging: Modify and experiment with kernel parameters in isolation
📚 Complete Documentation
| 📖 Guide | Description |
|---|---|
| 🏠 Wiki Home | Complete documentation and quick navigation |
| 📦 Installation | Setup guide for all scenarios |
| 📋 Usage Guide | Complete workflow, reproducer generation, and examples |
| 🌐 Web Interface | Master the visualization interface |
| 🔧 Developer Guide | Contributing and architecture overview |
| 📝 Code Formatting | Formatting standards and tools |
| ❓ FAQ | Quick answers and troubleshooting |
| ⚙️ Environment Variables | Complete environment variable reference |
| 📖 Python API Reference | Full API documentation |
| 🔄 Reproducer Guide | Comprehensive kernel reproducer guide |
📊 Understanding Triton Compilation
TritonParse visualizes the complete Triton compilation pipeline:
Python Source → TTIR → TTGIR → LLIR → PTX/AMDGCN
Each stage can be inspected and compared to understand optimization transformations.
🤝 Contributing
We welcome contributions! Please see our Developer Guide for:
- Development setup and prerequisites
- Code formatting standards (Formatting Guide)
- Pull request and code review process
- Testing guidelines
- Architecture overview
📞 Support & Community
- 🐛 Report Issues: GitHub Issues
- 💬 Discussions: GitHub Discussions
- 📚 Documentation: TritonParse Wiki
📄 License
This project is licensed under the BSD-3 License - see the LICENSE file for details.
✨ Ready to get started? Visit our Installation Guide or try the online tool directly!
1 maintainer
Release files for tritonparse 0.3.3.dev20251231071619
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| tritonparse-0.3.3.dev20251231071619.tar.gz | 534.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tritonparse-0.3.3.dev20251231071619-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 654.4 kB
Release files / tritonparse-0.3.3.dev20251231071619.tar.gz
| Download URL | tritonparse-0.3.3.dev20251231071619.tar.gz |
|---|---|
| Size | 534.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
406e6fd44dbce39f4149c565a91a2e84bd75000316ff111d7c703ced2f1b6c19
|
|
BLAKE2b-256 checksum How to use checksums |
f8a8b63c74f44490778061aeb83bf4929a96a4e9970ee35a72b6f15727d5b86e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 31, 2025.
Transparency logRelease files / tritonparse-0.3.3.dev20251231071619-py3-none-any.whl
| Download URL | tritonparse-0.3.3.dev20251231071619-py3-none-any.whl |
|---|---|
| Size | 120.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
38c0c5a9aad610ff0a541703e91b3b576c79ab0af3c8f170d1c729ca100b6da9
|
|
BLAKE2b-256 checksum How to use checksums |
5e8fc03c60513016e06258f3309f317c9350093c6421b64a2b9390123dc226ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 31, 2025.
Transparency log
