How to Trace Framework or Library Source Code Execution through VizTracer? #483
Replies: 2 comments 3 replies
-
|
The problem is - viztracer records function stack, you can't simply ignore an arbitrary piece of the stack and record the rest - the call relation would be messed up. So for viztracer, as long as you choose to ignore one function, you would ignore all it's sub-calls. I wouldn't recommend recording only code in a framework because normally that does not make sense - what if it calls to the standard library? Will the call be recorded? If the disk and the memory permits, it's better to record everything. If you do need to only record piece of code, you can try |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much for your prompt reply! I really appreciate your detailed explanation, and now I fully understand how to proceed based on your suggestion. Also, VizTracer has been very helpful for my work—great tool! |
Beta Was this translation helpful? Give feedback.
-
|
@gaogaotiantian , I almost agree, however, what if I'm interested the under the hood of a library and not want to get noise from asyncio or others. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
There are a few ways to do it. You can use |
Beta Was this translation helpful? Give feedback.
-
|
@AnElegantHusky , did you manage to figure this one out? I'm also interested in just tracing a library. |
Beta Was this translation helpful? Give feedback.
-
I am currently using VizTracer to trace the execution of a framework or library's source code. I attempted to include the source files by using the
--include_filesoption, but I only managed to capturebuiltins.exec.Does anyone have experience with tracing the execution of specific library or framework source code using VizTracer? Is there a different approach I should be using?
Any guidance or suggestions would be greatly appreciated. Thank you!
Beta Was this translation helpful? Give feedback.
All reactions