-
Notifications
You must be signed in to change notification settings - Fork 54
Add NVTX marker instrumentation #2345
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
Open
iomaganaris
wants to merge
5
commits into
GridTools:main
Choose a base branch
from
iomaganaris:nvtx_markers
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+14
−1
Open
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
ed529bc
Add NVTX marker instrumentation
iomaganaris 494570b
Make sure that instrumentation reports from dace are not written in e…
iomaganaris 9fc1764
Added comment for map entries
iomaganaris ad794c9
Merge branch 'main' into nvtx_markers
iomaganaris 71a18bf
Merge branch 'main' into nvtx_markers
iomaganaris 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 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
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
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.
Your current check is at compile time. The check in the instrumentation above is at runtime. I propose to always add NVTX instrumentation, because the
config.COLLECT_METRICS_LEVELvalue is meant to be a runtime setting. It is still possible to skip SDFG instrumentation by settinguse_metrics=Falseon the dace backend, at compile-time.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.
I am not sure I would be up to enabling NVTX ranges by default since they will add some (really minimal) overhead to the CPU side. If
use_metrics=Falsecan be set by default then it would be fine but it would increase some more complexity for production and profiling runs