[cuda.coop]: add device-side coop.warp.sum benchmark with pynvbench
#6846
+207
−0
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
closes #6606
This adds a Python benchmark using pynvbench for
coop.warp.sum. This was already done in C++ in #6431, this reimplements it in Python.Comparing the two, we get these results from the pre-existing C++ benchmark (I deleted the results for types we don't support in cuda.coop right now):
and these results from the new Python benchmark
The GPU Times for both are identical but the Python implementation has larger CPU Times, likely due to overhead introduced by the numba-cuda kernel call.
One other thing of note is that the SASS for two versions are identical, except for an extra NOP in the Python version that appears after the redux instruction:
I spent some time investigating this and I have a minimal reproducer that shows issue is from numba-cuda. Will open an issue to track this.
This PR will also introduce pynvbench as an optional dependency (haven't implemented this yet).
Checklist