TileLens: A Visualization Toolkit for programming with Triton
Welcome to TileLens, a visualization and profiling toolkit designed for deep learning applications. Built with the intention of making kernel programming in tile-based DSLs like Triton more intuitive.
TileLens helps developers inspect Triton kernels with visualization, profiling, and memory-safety analysis tools. It can run many examples through Triton’s interpreter, so GPU access is not required for basic debugging workflows.
Getting Started
Prerequisites
Python >= 3.10
Installation of TileLens
Windows Note: TileLens depends on Triton, which can only be installed on Windows Subsystem for Linux (WSL). Once installed, follow below instructions in WSL.
Install TileLens from PyPI:
pip install tilelens
If you want to run examples from this repo, contribute, or build the web UI, install from source instead:
git clone https://github.com/Deep-Learning-Profiling-Tools/tilelens.git
cd tilelens
uv sync # or "uv sync --extra test" if you're running tests
Transitioning from Triton-viz to TileLens
The GitHub repo and PyPI package are now named tilelens. Use import tilelens
in new code. Old triton_viz imports, including submodule imports, still work.
If you already have triton-viz installed, uninstall it before installing
TileLens. The two packages share files, so keeping both installed can break
imports and CLI commands:
pip uninstall -y triton-viz
pip install tilelens
For source installs, use pip install . after uninstalling the old package.
If you already installed both, uninstall triton-viz first, then run
pip install --force-reinstall --no-deps tilelens (or
pip install --force-reinstall --no-deps . from this repo). This restores the
shared files without reinstalling or upgrading dependencies such as Triton.
Restart Python or your notebook kernel after upgrading.
Existing .tvz traces can still be loaded with tilelens.load(...).
Traces saved by TileLens cannot be loaded by older Triton-Viz versions.
CLI commands are tile-sanitizer, tile-profiler, tile-race, and tile-visualizer.
The old triton-sanitizer, triton-profiler, triton-race-detector, and
triton-visualizer commands still work.
Web UI Build
The PyPI package ships with prebuilt web UI assets in tilelens/static, so
you do not need npm to run the visualizer. If you want to modify the web UI,
rebuild the TS sources:
npm install
npm run build:frontend
Optional: Enable NKI Support
For PyPI installs, install with the nki extra and AWS Neuron repository:
uv sync --extra nki # or "uv sync --extra nki --extra test" if also running NKI-related tests
Note that you need to specify all features that you want in one statement when using uv sync, i.e. if you want both NKI and testing support, you must run uv sync --extra nki --extra test. The below statements are wrong and will remove the NKI install when installing test packages:
uv sync --extra nki # NKI support but no testing
uv sync --extra test # tests but no NKI support
Testing
To run core TileLens tests, run pytest tests/.
(if NKI installed) To run NKI-specific tests, run pytest tests/ -m nki.
To run all tests (Triton + NKI), run pytest tests/ -m "".
To run visualizer web UI tests, run npm run test:frontend.
Working with Examples
Run an example directly with Python:
python examples/visualizer/matmul.py
Use the decorator API when writing or modifying a Triton kernel:
Use the CLI wrappers to run an existing Python script without editing it. These
wrappers patch plain @triton.jit kernels, so use them with scripts that do not
already apply @tilelens.trace(...).
The runtime integration code lives under tilelens/core/frontend/. NKI
simulation runtimes live under tilelens/core/simulation/.
Analysis Clients
Analyze kernels across visualization, profiling, and sanitization with a single line of code.
Visualizer: currently supports load, store, and matmul operations for 1/2/3D tensors (more operations and dimensions coming soon).
Profiler: flags non-unrolled loops, inefficient mask usage, and missing buffer_load optimizations while tracking load/store byte counts with low-overhead sampling.
Sanitizer: symbolically checks tensor memory accesses for out-of-bounds errors and emits reports with tensor metadata, call stack, and expression trees; optional fake-memory storage avoids real reads.
Save and load traces
import tilelens
tilelens.save("trace.tvz")
tilelens.load(
"trace.tvz"
) # automatically clears out existing records, use kwarg "append=True" to prevent this
tilelens.launch()
CLI: tile-visualizer trace.tvz. The archive is a zip file containing manifest.json plus tensors.npz, and tilelens.load(...) restores the normal trace state for existing consumers.
Environment variables
TileLens uses a small set of environment variables to configure runtime behavior. Unless noted, boolean flags are enabled only when set to 1.
The old names TRITON_VIZ_VERBOSE, TRITON_VIZ_NUM_SMS, and TRITON_VIZ_PORT
still work. If both names are set, TileLens uses the TILELENS_* value.
TILELENS_VERBOSE (default: 0): enable verbose logging and extra debug output.
TILELENS_NUM_SMS (default: 1): number of concurrent SMs to emulate for the CPU interpreter (min 1).
TILELENS_PORT (default: 8000 with share=True, 5001 with share=False): port for the Flask server.
ENABLE_SANITIZER (default: 1): enable the sanitizer pipeline that checks memory accesses.
ENABLE_PROFILER (default: 1): enable the profiler pipeline that collects performance data.
ENABLE_TIMING (default: 0): collect timing data during execution.
REPORT_GRID_EXECUTION_PROGRESS (default: 0): report per-program block execution progress in the interpreter.
SANITIZER_ENABLE_FAKE_TENSOR (default: 0): use fake tensor storage for sanitizer runs to avoid real memory reads.
PROFILER_ENABLE_BLOCK_SAMPLING (default: 1): sample a subset of blocks to reduce profiling overhead.
PROFILER_DISABLE_BUFFER_LOAD_CHECK (default: 0): disable buffer load checks in the profiler.
More Puzzles
If you’re interested in fun puzzles to work with in Triton, do check out: Triton Puzzles
License
TileLens is licensed under the MIT License. See the LICENSE for details.
Publication
If you find this repo useful for your research, please cite our paper:
@inproceedings{ramesh2025tritonviz,
author={Ramesh, Tejas and Rush, Alexander and Liu, Xu and Yin, Binqian and Zhou, Keren and Jiao, Shuyin},
title={Triton-Viz: Visualizing GPU Programming in AI Courses},
booktitle = {Proceedings of the 56th ACM Technical Symposium on Computer Science Education (SIGCSE TS '25)},
numpages = {7},
location = {Pittsburgh, Pennsylvania, United States},
series = {SIGCSE TS '25}
}
@inproceedings{wu2026tritonsanitizer,
author = {Wu, Hao and Zhao, Qidong and Chen, Songqing and Chen, Yang and Hao, Yueming and Liu, Tony C. W. and Chen, Sijia and Aziz, Adnan and Zhou, Keren},
title = {Triton-Sanitizer: A Fast and Device-Agnostic Memory Sanitizer for Triton with Rich Diagnostic Context},
year = {2026},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
location = {Pittsburgh, PA, USA},
booktitle = {Proceedings of the 31st ACM International Conference on Architectural Support for Programming Languages and Operating Systems},
series = {ASPLOS '26},
keywords = {GPU, Debugging, Symbolic Execution, Memory Safety, Triton, Memory Access Errors}
}
TileLens: A Visualization Toolkit for programming with Triton
Welcome to TileLens, a visualization and profiling toolkit designed for deep learning applications. Built with the intention of making kernel programming in tile-based DSLs like Triton more intuitive.
Visit our site to see our tool in action!
Table of Contents
About
TileLens helps developers inspect Triton kernels with visualization, profiling, and memory-safety analysis tools. It can run many examples through Triton’s interpreter, so GPU access is not required for basic debugging workflows.
Getting Started
Prerequisites
Installation of TileLens
Install TileLens from PyPI:
If you want to run examples from this repo, contribute, or build the web UI, install from source instead:
Transitioning from Triton-viz to TileLens
The GitHub repo and PyPI package are now named
tilelens. Useimport tilelensin new code. Oldtriton_vizimports, including submodule imports, still work.If you already have
triton-vizinstalled, uninstall it before installing TileLens. The two packages share files, so keeping both installed can break imports and CLI commands:For source installs, use
pip install .after uninstalling the old package. If you already installed both, uninstalltriton-vizfirst, then runpip install --force-reinstall --no-deps tilelens(orpip install --force-reinstall --no-deps .from this repo). This restores the shared files without reinstalling or upgrading dependencies such as Triton. Restart Python or your notebook kernel after upgrading.Existing
.tvztraces can still be loaded withtilelens.load(...). Traces saved by TileLens cannot be loaded by older Triton-Viz versions.CLI commands are
tile-sanitizer,tile-profiler,tile-race, andtile-visualizer. The oldtriton-sanitizer,triton-profiler,triton-race-detector, andtriton-visualizercommands still work.Web UI Build
The PyPI package ships with prebuilt web UI assets in
tilelens/static, so you do not need npm to run the visualizer. If you want to modify the web UI, rebuild the TS sources:Optional: Enable NKI Support
For PyPI installs, install with the
nkiextra and AWS Neuron repository:For source installs:
Note that you need to specify all features that you want in one statement when using
uv sync, i.e. if you want both NKI and testing support, you must runuv sync --extra nki --extra test. The below statements are wrong and will remove the NKI install when installing test packages:Testing
pytest tests/.pytest tests/ -m nki.pytest tests/ -m "".npm run test:frontend.Working with Examples
Run an example directly with Python:
Use the decorator API when writing or modifying a Triton kernel:
Use the CLI wrappers to run an existing Python script without editing it. These wrappers patch plain
@triton.jitkernels, so use them with scripts that do not already apply@tilelens.trace(...).For visualizer workflows, save a trace and launch the UI from Python:
DSL Frontends
Triton is the default DSL frontend. NKI support is optional and selected with the
frontendargument:The runtime integration code lives under
tilelens/core/frontend/. NKI simulation runtimes live undertilelens/core/simulation/.Analysis Clients
Analyze kernels across visualization, profiling, and sanitization with a single line of code.
Save and load traces
CLI:
tile-visualizer trace.tvz. The archive is a zip file containingmanifest.jsonplustensors.npz, andtilelens.load(...)restores the normal trace state for existing consumers.Environment variables
TileLens uses a small set of environment variables to configure runtime behavior. Unless noted, boolean flags are enabled only when set to
1.The old names
TRITON_VIZ_VERBOSE,TRITON_VIZ_NUM_SMS, andTRITON_VIZ_PORTstill work. If both names are set, TileLens uses theTILELENS_*value.TILELENS_VERBOSE(default:0): enable verbose logging and extra debug output.TILELENS_NUM_SMS(default:1): number of concurrent SMs to emulate for the CPU interpreter (min 1).TILELENS_PORT(default:8000withshare=True,5001withshare=False): port for the Flask server.ENABLE_SANITIZER(default:1): enable the sanitizer pipeline that checks memory accesses.ENABLE_PROFILER(default:1): enable the profiler pipeline that collects performance data.ENABLE_TIMING(default:0): collect timing data during execution.REPORT_GRID_EXECUTION_PROGRESS(default:0): report per-program block execution progress in the interpreter.SANITIZER_ENABLE_FAKE_TENSOR(default:0): use fake tensor storage for sanitizer runs to avoid real memory reads.PROFILER_ENABLE_LOAD_STORE_SKIPPING(default:1): skip redundant load/store checks to reduce profiling overhead.PROFILER_ENABLE_BLOCK_SAMPLING(default:1): sample a subset of blocks to reduce profiling overhead.PROFILER_DISABLE_BUFFER_LOAD_CHECK(default:0): disable buffer load checks in the profiler.More Puzzles
If you’re interested in fun puzzles to work with in Triton, do check out: Triton Puzzles
License
TileLens is licensed under the MIT License. See the LICENSE for details.
Publication
If you find this repo useful for your research, please cite our paper:
(back to top)