chore: add flamegraph instructions for profiling - #318
Open
alxiong wants to merge 5 commits into
Open
Conversation
4 tasks
Contributor
Author
|
Hold on merging perhaps, I might want to explore more other tools with different presentation on the profiled performance. |
ggutoski
reviewed
Jun 14, 2023
alxiong
force-pushed
the
flamegraph
branch
2 times, most recently
from
June 15, 2023 13:14
5d9ab4b to
1620f33
Compare
alxiong
force-pushed
the
flamegraph
branch
2 times, most recently
from
June 15, 2023 14:45
f863992 to
4b4827d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add
cargo-flamegraphto nix-shell and add instructions to demonstrate how to run in in README.Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
Wrote unit testsAdded a relevant changelog entry to thePendingsection inCHANGELOG.mdFiles changedin the GitHub PR explorer