Execution Provider Profiler#8406
Merged
Merged
Conversation
RandySheriffH
changed the title
snnn
reviewed
Sep 27, 2021
| @@ -1,2 +1,2 @@ | |||
| set PATH=C:\azcopy;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.1\bin;C:\local\cudnn-11.4-windows-x64-v8.2.2.26\cuda\bin;%PATH% | |||
| set PATH=C:\azcopy;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.1\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.4\extras\CUPTI\lib64;C:\local\cudnn-11.4-windows-x64-v8.2.2.26\cuda\bin;%PATH% | |||
Contributor
There was a problem hiding this comment.
You may get this file unchanged. The file is not referenced anywhere.
snnn
approved these changes
Sep 27, 2021
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
3 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.
Implement cuda profiler by cupti library. With profiling enabled, all triggerred cuda kernels will be logged.
Correlation between ops and kernels are established along the profiling - in final output, related kernel logs will be placed under the op with the same op_name:
[
...
{"cat" : "Node","pid" :12572,"tid" :9380,"dur" :24,"ts" :6770761,"ph" : "X","name" :"Add_0_fence_before","args" : {"op_name" : "Add"}},
{"cat" : "Kernel","pid" :-1,"tid" :-1,"dur" :4,"ts" :6771333,"ph" : "X","name" :"BinaryElementWiseKernel","args" : {"op_name" : "Add","stream" : "13","block_x" : "256","grid_x" : "1","grid_y" : "1","grid_z" : "1","block_y" : "1","block_z" : "1"}},
...
]