CUPTI metrics for bloom_filter benchmarks #609
Merged
+20
−15
Conversation
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
sleeepyjack
added
P2: Nice to have
|
@sleeepyjack, could you please share the new benchmark results in the comments for reference? |
Merged
|
Here they are: #573 (comment) |
PointKernel
approved these changes
Oct 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces collecting CUPTI metrics (DRAM throughput, cache hit rates, etc.) during the
cuco::bloom_filterbenchmark.Additionally, the benchmark now uses the default
pattern_bitsvalue for a given policy instead of hardcoding it to 8.