Viztracer
A debugging and profiling tool that can trace and visualize python code execution
Install / Use
/learn @gaogaotiantian/ViztracerREADME
VizTracer
VizTracer is a low-overhead logging/debugging/profiling tool that can trace and visualize your python code execution.
The front-end UI is powered by Perfetto. Use "AWSD" to zoom/navigate. More help can be found in "Support - Controls".
Highlights
- Detailed function entry/exit information on timeline with source code
- Super easy to use, no source code change for most features, no package dependency
- Low overhead, probably the fastest tracer in the market
- Supports threading, multiprocessing, subprocess, async and PyTorch
- Powerful front-end, able to render GB-level trace smoothly
- Works on Linux/MacOS/Windows
Install
The preferred way to install VizTracer is via pip
pip install viztracer
Basic Usage
Command Line
# Instead of "python3 my_script.py arg1 arg2"
viztracer my_script.py arg1 arg2
<details>
<summary>
A <code>result.json</code> file will be generated, which you can open with <code>vizviewer</code>
</summary>
# You can display all the files in a directory and open them in browser too
vizviewer ./
# For very large trace files, try external trace processor
vizviewer --use_external_processor result.json
vizviewer will host an HTTP server on http://localhost:9001. You can also open your browser and use that address.
If you do not want vizviewer to open the webbrowser automatically, you can use
vizviewer --server_only result.json
If you just need to bring up the trace report once, and do not want the persistent server, use
vizviewer --once result.json
</details>
vizviewer result.json
A VS Code Extension is available to make your life even easier.
<p align="center"> <img src="https://github.com/gaogaotiantian/viztracer-vscode/raw/master/assets/demo.gif" /> </p> <details> <summary> Add <code>--open</code> to open the reports right after tracing </summary>viztracer --open my_script.py arg1 arg2
viztracer -o result.html --open my_script.py arg1 arg2
</details>
<details>
<summary>
modules and console scripts(like <code>flask</code>) are supported as well
</summary>
viztracer -m your_module
viztracer flask run
</details>
Inline
You can also manually start/stop VizTracer in your script as well.
from viztracer import VizTracer
tracer = VizTracer()
tracer.start()
# Something happens here
tracer.stop()
tracer.save() # also takes output_file as an optional argument
Or, you can do it with with statement
with VizTracer(output_file="optional.json") as tracer:
# Something happens here
Jupyter
If you are using Jupyter, you can use viztracer cell magics.
# You need to load the extension first
%load_ext viztracer
%%viztracer
# Your code after
A VizTracer Report button will appear after the cell and you can click it to view the results
PyTorch
VizTracer can log native calls and GPU events of PyTorch (based on torch.profiler) with
--log_torch.
with VizTracer(log_torch=True) as tracer:
# Your torch code
viztracer --log_torch your_model.py
Advanced Usage
Trace Filter
VizTracer can filter out the data you don't want to reduce overhead and keep info of a longer time period before you dump the log.
Extra Logs without Code Change
VizTracer can log extra information without changing your source code
- Any Variable/Attribute with RegEx
- Function Entry
- Variables in Specified Function
- Garbage Collector Operation
- Function Input Arguments
- Function Return Value
- Audit Events
- Raised Exceptions
Add Custom Event
VizTracer supports inserting custom events while the program is running. This works like a print debug, but you can know when this print happens while looking at trace data.
Misc
Multi Thread Support
For Python3.12+, VizTracer supports Python-level multi-thread tracing without the need to do any modification to your code.
For versions before 3.12, VizTracer supports python native threading module. Just start VizTracer before you create threads and it will just work.
For other multi-thread scenarios, you can use enable_thread_tracing() to notice VizTracer about the thread to trace it.
Refer to multi thread docs for details
Multi Process Support
VizTracer supports subprocess, multiprocessing, os.fork(), concurrent.futures, and loky out of the box.
For more general multi-process cases, VizTracer can support with some extra steps.
Refer to multi process docs for details
Async Support
VizTracer supports asyncio natively, but could enhance the report by using --log_async.
Refer to async docs for details
Flamegraph
Perfetto supports native flamegraph, just select slices on the UI and choose "Slice Flamegraph".
Remote attach
VizTracer supports remote attach to an arbitrary Python process to trace it, as long as viztracer is importable
Refer to remote attach docs
JSON alternative
VizTracer needs to dump the internal data to json format. It is recommended for the users to install orjson, which is much faster than the builtin json library. VizTracer will try to import orjson and fall back to the builtin json library if orjson does not exist.
Performance
VizTracer puts in a lot of effort to achieve low overhead. The actual performance impact largely depends on your application. For typical codebases, the overhead is expected to be below 1x. If your code has infrequent function calls, the overhead could be minimal.
<details> <summary> Detailed explanation </summary>The overhead introduced by VizTracer is basically a fixed amount of time during function entry and exit, so the more time spent on function entri





