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
- 🚀 Launch Difference Analysis - Automatically detect and visualize variations in kernel launch parameters, helping you pinpoint performance bottlenecks and debug launch configurations.
- 🔍 Interactive Visualization - Explore Triton kernels with detailed metadata and stack traces
- 📊 Multi-format IR Support - View TTGIR, TTIR, LLIR, PTX, and AMDGCN in one place
- 🔄 Side-by-side Comparison - Compare IR stages with synchronized highlighting
- 📝 Structured Logging - Capture detailed compilation and launch events with source mapping
- 🌐 Ready-to-use Interface - No installation required, works in your browser
- 🔒 Privacy-first - All processing happens locally in your browser, no data uploaded
🚀 Quick Start
1. Generate Traces
import tritonparse.structured_logging
# Initialize logging with launch tracing enabled
tritonparse.structured_logging.init("./logs/", enable_trace_launch=True)
# Your Triton/PyTorch code here
# ... your kernels ...
# Parse and generate trace files
import tritonparse.utils
tritonparse.utils.unified_parse("./logs/")
The example terminal output is:
tritonparse log file list: /tmp/tmp1gan7zky/log_file_list.json
INFO:tritonparse:Copying parsed logs from /tmp/tmp1gan7zky to /scratch/findhao/tritonparse/tests/parsed_output
================================================================================
📁 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!
================================================================================
2. 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!
🛠️ Installation
For basic usage (trace generation): Four options:
# 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. Please install the latest version of Triton:
pip install triton
📚 Complete Documentation
| 📖 Guide | Description |
|---|---|
| 🏠 Wiki Home | Complete documentation and navigation |
| 📦 Installation Guide | Detailed setup for all scenarios |
| 📋 Usage Guide | Complete workflow and examples |
| 🌐 Web Interface Guide | Master the visualization interface |
| 🔧 Developer Guide | Contributing and development setup |
| ❓ FAQ | Frequently asked questions |
🛠️ Tech Stack
- Frontend: React 19, TypeScript, Vite, Tailwind CSS, Monaco Editor
- Backend: Python with Triton integration, structured logging
- Deployment: GitHub Pages, automatic deployment
📊 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
- Code formatting standards
- Pull request process
- 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!
Metadata
Release files for tritonparse 0.2.4.dev20251001071529
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tritonparse-0.2.4.dev20251001071529.tar.gz | 2.6 MB | Without provenance | Details for tritonparse-0.2.4.dev20251001071529.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tritonparse-0.2.4.dev20251001071529-py3-none-any.whl | Python 3 | none | any | Details for tritonparse-0.2.4.dev20251001071529-py3-none-any.whl |
Total release size: 2.7 MB
Release files / tritonparse-0.2.4.dev20251001071529.tar.gz
| Download URL | tritonparse-0.2.4.dev20251001071529.tar.gz |
|---|---|
| Size | 2.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5579944751efe124fda6e2b5831ee163ed5b005f1173bd72b51d3ae9f76b85a1
|
|
BLAKE2b-256 checksum How to use checksums |
8025bd3d1d50ada3ed2d6d15b2f244c0aee553eedb88b0af4c8fbdb8c16bfcba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / tritonparse-0.2.4.dev20251001071529-py3-none-any.whl
| Download URL | tritonparse-0.2.4.dev20251001071529-py3-none-any.whl |
|---|---|
| Size | 55.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9d7a707b617c595f7dfc9957c1d462bc4fcd9710fcee955336a630c58d1417b2
|
|
BLAKE2b-256 checksum How to use checksums |
ffbd7876c8818ae53df6da17e5a634624cc9bafd9972bb4d35c8b7b83d3022bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for tritonparse 0.2.4.dev20251001071529
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.