Repository navigation
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.
Keep HIP runtime overhead out of benchmark measurements #2464
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
base: develop
Are you sure you want to change the base?
Keep HIP runtime overhead out of benchmark measurements #2464
Changes from all commits
a9982efFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
This eager prepare only covers the
--triton-benchmark-modebranch, but the legacy default path has the same defect. InmeasureSmallKernelthe CPU timer starts at line 470 and the firstflushInstructionCache/flushCachehappens at lines 475-478, i.e. inside the timed region — so on the very first config of a tuning run the hiprtc compile plus the (up to 256 MiB with--flush-last-level-cache)hipMallocis charged tosmallKernelCpuMs. Since legacy mode is the default and tuning mode is exactly the case wherebenchmarkModeis false and the flushes do run, that first perf config gets a badly inflated time and can be ranked out even when it is the best one. Suggest hoisting the call above theif (!params.tritonBenchmarkMode)at line 670 so both paths get the artifacts built up front; if you want to avoid the large allocation in the legacy path that never flushes, gate it onparams.tritonBenchmarkMode || params.benchmarkConfig.empty()instead of duplicating the call. (Checklist: Major — "DRY/YAGNI/KISS violations: redundant code" / incomplete fix across equivalent code paths.)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.
@dhernandez0 I agree with this one, please take a look
Uh oh!
There was an error while loading. Please reload this page.