Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
OpenDAS
vllm_cscc
Commits
fb7abfc1
Unverified
Commit
fb7abfc1
authored
Jan 27, 2026
by
Angela Yi
Committed by
GitHub
Jan 28, 2026
Browse files
[docs] Improve tlparse section (#33211)
Signed-off-by:
angelayi
<
yiangela7@gmail.com
>
parent
5d3d6e44
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
7 deletions
+12
-7
docs/design/debug_vllm_compile.md
docs/design/debug_vllm_compile.md
+12
-7
No files found.
docs/design/debug_vllm_compile.md
View file @
fb7abfc1
...
@@ -39,10 +39,9 @@ For more details on the design, please see the following resources:
...
@@ -39,10 +39,9 @@ For more details on the design, please see the following resources:
## Use tlparse
## Use tlparse
Use
[
tlparse
](
https://github.com/meta-pytorch/tlparse
)
to acquire torch.compile logs. These logs show all stages of the compilation process,
Use
[
tlparse
](
https://github.com/meta-pytorch/tlparse
)
to view torch.compile
including the fused kernels that torch.compile produces.
logs. These logs show all stages of the compilation process, including the fused
If you can, we recommend sending these or pieces of these along with any bug reports --
kernels that torch.compile produces.
they are very helpful.
Install tlparse:
Install tlparse:
...
@@ -50,11 +49,16 @@ Install tlparse:
...
@@ -50,11 +49,16 @@ Install tlparse:
pip
install
tlparse
pip
install
tlparse
```
```
To enable the torch.compile logs, you can set the envvar
`TORCH_TRACE=<dir>`
.
During tracing, a file per rank will be created inside of that directory, with
each file containing the artifacts during compilation. If you can, we recommend
sending these log files along with bug reports -- they are very helpful.
Usage (offline inference)
Usage (offline inference)
```
sh
```
sh
TORCH_TRACE
=
~/trace_dir python my_script.py
TORCH_TRACE
=
~/trace_dir python my_script.py
tlparse ~/trace_dir/<
the_first
_log_file>
tlparse ~/trace_dir/<
rank_0
_log_file>
```
```
Usage (serving)
Usage (serving)
...
@@ -62,10 +66,11 @@ Usage (serving)
...
@@ -62,10 +66,11 @@ Usage (serving)
```
sh
```
sh
TORCH_TRACE
=
~/trace_dir vllm serve
TORCH_TRACE
=
~/trace_dir vllm serve
# ctrl-c out of the server
# ctrl-c out of the server
tlparse ~/trace_dir/<
the_first
_log_file>
tlparse ~/trace_dir/<
rank_0
_log_file>
```
```
The
`tlparse`
command outputs some HTML files (perhaps into e.g.
`./tl_out/index.html`
).
Given one of the log files, the
`tlparse`
command outputs some HTML files
(perhaps into e.g.
`./tl_out/index.html`
).
Open it to see the logs. It'll look something like the following:
Open it to see the logs. It'll look something like the following:


...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment