-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Add more arguments to x perf
#126853
Closed
Closed
Add more arguments to x perf
#126853
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
5cf01b8
Add CLI arguments for `x perf`
Kobzol d827acb
Add more CLI options to `x perf`
Kobzol d5a01b5
Add Samply and Cachegrind profilers to `x perf`
Kobzol fa340b4
Regenerate terminal completions
Kobzol a29b18a
Make `samply` installation command better
Kobzol File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we run all the benchmarks by default with something like
PerfCommand::All
when the user doesn't specify a particular benchmark module (e.g.,x perf
)?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to clarify, these are individual profilers (
eprintln
,cachegrind
, etc.), not benchmarks. I don't think that it makes sense to run all of them at once, it's like runningcargo check/build/test
at once, they just do very different things and serve different purposes. We could select some default, but I'm not sure if there even is a default profiler.Once we actually add benchmarking in the future, I would propose
x perf
to just run benchmarks, but since we only have profilers now, I would opt into requiring users to select the profiler that they want to use.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO it makes more sense to run
samply
(perhaps even together withcachegrind
) rather than runningeprintln
by default. Currently theeprintln
default doesn't really provide a good overall report about the compiler.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, just to clarify, I would prefer to keep the current situation, where you cannot just do
x perf
, but you have to select some profiler. Because currently I don't think there is a good default - for bothsamply
andcachegrind
, you need to have an external tool installed, so that isn't IMO a good default.This
Default
implementation should be basicallyunreachable!
.