-
Notifications
You must be signed in to change notification settings - Fork 147
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
[Feature Request] Show Progress #270
Comments
Unfortunately I don't have much time for maintaining flamegraph. Maybe consider submitting a PR? |
Is there any doc about the overall structure/execution path of this project? I'm willing to have a try but don't know where to start. |
No, but it's pretty simple. We get the inferno crate to collapse the data at https://github.com/flamegraph-rs/flamegraph/blob/main/src/lib.rs#L367 and generate the flamegraph at https://github.com/flamegraph-rs/flamegraph/blob/main/src/lib.rs#L427. You should figure which of those is slow. Then, I think you might want to wrap an indicatif thing around the input to either of those things (or both?). |
Also, for me, the bottleneck appears to be Line 128 in 1aeb2a8
Is this surprising to you? (I don't know what this command does.) |
Unless you've specifically enabled I don't know much about If it doesn't work well for you, consider trying samply instead -- it seems to work better on macOS at least, and @mstange is a lot more knowledgeable about |
This is a problem which I had, so I can probably take a stab at adding this feature. Implementing a true progress bar with perf script is not obvious to me, but I think a spinner with a message about what is running and an elapsed time is a good start, and that is fairly simple to add. |
Perf script can take a long time to run. This change adds an indicator to show that it is running so that the user knows that their application is not causing the terminal to hang. Addresses flamegraph-rs#270
Perf script can take a long time to run. This change adds an indicator to show that it is running so that the user knows that their application is not causing the terminal to hang. Addresses flamegraph-rs#270
Perf script can take a long time to run. This change adds an indicator to show that it is running so that the user knows that their application is not causing the terminal to hang. Addresses flamegraph-rs#270
Perf script can take a long time to run. This change adds an indicator to show that it is running so that the user knows that their application is not causing the terminal to hang. Addresses flamegraph-rs#270
Perf script can take a long time to run. This change adds an indicator to show that it is running so that the user knows that their application is not causing the terminal to hang. Addresses flamegraph-rs#270
Ok, after a few different iterations, I found something that I like and it is available as a PR at #343 |
Perf script can take a long time to run. This change adds an indicator to show that it is running so that the user knows that their application is not causing the terminal to hang. Addresses flamegraph-rs#270
Perf script can take a long time to run. This change adds an indicator to show that it is running so that the user knows that their application is not causing the terminal to hang. Addresses flamegraph-rs#270
Perf script can take a long time to run. This change adds an indicator to show that it is running so that the user knows that their application is not causing the terminal to hang. Addresses #270
In my case,
perf.data
is huge(10GB+) and usually takes 30+ min to generate the flame graph.It will be much more friendly if there is a progress bar.
The text was updated successfully, but these errors were encountered: