Repository navigation
test(rocprofiler-sdk): range replay week of 2026-11-02: P1 (stacked) - #14806
Draft
amd-vkale wants to merge 2 commits into
Conversation
Add a nightly perf check that times dispatches with range replay configured but no range opened, against the same workload with no tool. The tool aborts if any range closes, so the ratio cannot be read from an accidental replay window. Co-authored-by: Vivek Kale <vivek.kale@amd.com>
The performance coverage row and the missing-tests preamble now name the idle-gate overhead measurement. Co-authored-by: Vivek Kale <vivek.kale@amd.com>
github-actions
Bot
added
documentation
This was referenced Nov 6, 2026
This branch has not been deployed
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
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.
Motivation
Weekly range-replay test addition for the week of 2026-11-02 from the range replay test plan: P1, the idle-gate overhead when range replay is configured but no range is ever opened.
Stacked on the week-of-2026-10-26 tip (C5, C6).
Technical Details
Extends
tests/range-replay-perf/with a nightly-only check (ROCPROFILER_BUILD_NIGHTLY_PERF_CTESTS):RR_PERF_IDLE_GATE=1times a burst of dispatches without callingbegin/end.RR_PERF_EXPECT_IDLE=1configures the range-replay service and aborts if any range closes, so the ratio cannot be read from an accidental replay window.run_idle_overhead.pycompares median wall time with the tool against the same workload with no tool (noLD_PRELOAD), and requires the ratio to stay at or under 2.0.The process-wide interception gate is what this measures: with range replay configured, every submission still enters
range_replay::submission_hook, which is a no-op when no range is open.Roadmap coverage row and the missing-tests preamble now name P1.
Issue Tracking
Related: #10864 (range replay service).
Test Plan
g++ -fsyntax-onlyonclient.cppand a HIP-host rewrite ofmain.cppagainst in-tree headers.python3 -m py_compile/ import check onrun_idle_overhead.py.Test Result
Host syntax and format checks passed. GPU idle-gate timing was not run here.
Submission Checklist