Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get the call stack trace(s) in the UI #748

Open
rben-dev opened this issue Dec 21, 2023 · 2 comments
Open

Get the call stack trace(s) in the UI #748

rben-dev opened this issue Dec 21, 2023 · 2 comments

Comments

@rben-dev
Copy link

rben-dev commented Dec 21, 2023

Is your feature request related to a problem? Please describe.
Sorry if I missed this, but the --stacks command line toggle activates stack traces collection (which can be indeed found in the produced json file), but nothing in the UI seems to relate to this.

Describe the solution you'd like
Get a view of the most significant (in the sense of CPU/GPU/memory usage) call trace(s) when hovering over a line or a function.

Additional context
When profiling a rather complex code where a line (e.g. a constructor of a class) is called multiple times in multiple contexts, it can be difficult to spot the call trace leading to the "hot spot" (consuming the most CPU/GPU/memory). I might however have missed a way of dealing with such situations (?)

@rben-dev rben-dev changed the title Get the stack call trace(s) in the UI Get the call stack trace(s) in the UI Dec 21, 2023
@FergusFettes
Copy link

I'm think I'm looking for the same thing: maybe this works for you?

https://github.com/joerick/pyinstrument

@mcarans
Copy link

mcarans commented Jul 12, 2024

Having the stack trace in the UI would be really useful. I tried pyinstrument but it uses too much memory when profiling my application.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants