Skip to content

perf(spark-runtime): opt-in NVTX kernel-attribution + phase-timing instrumentation#255

Open
Sujimoshi wants to merge 1 commit into
Avarok-Cybersecurity:mainfrom
Sujimoshi:perf/dflash-nvtx-instrumentation
Open

perf(spark-runtime): opt-in NVTX kernel-attribution + phase-timing instrumentation#255
Sujimoshi wants to merge 1 commit into
Avarok-Cybersecurity:mainfrom
Sujimoshi:perf/dflash-nvtx-instrumentation

Conversation

@Sujimoshi

Copy link
Copy Markdown
Contributor

Summary

First of a planned split of #218 (DFlash speculative decoding) into smaller, independently reviewable PRs — see the split plan discussed on #218. This PR carries only the diagnostic instrumentation slice:

  • crates/spark-runtime/src/nvtx_diag.rs (new) — opt-in NVTX range instrumentation for kernel attribution, gated behind ATLAS_NVTX_DIAG=1
  • crates/spark-runtime/src/kernel_args.rs — per-op timing/profiling hooks
  • libloading dependency, dlopen'd lazily — normal builds/runs have no link-time or runtime dependency on libnvToolsExt

No behavior change to any existing code path — purely additive, opt-in diagnostics.

Test plan

  • cargo check -p spark-runtime (ATLAS_SKIP_BUILD=1, CUDA stubbed) — clean
  • cargo fmt --check -p spark-runtime — clean
  • cargo clippy -p spark-runtime --tests (ATLAS_SKIP_BUILD=1) — no warnings
  • Runtime smoke test with ATLAS_NVTX_DIAG=1 on GB10 (requires live GPU, not exercised by this diff alone since it's dead code until wired up by later PRs in the split)

🤖 Generated with Claude Code

…strumentation

Diagnostic-only (ATLAS_NVTX_DIAG=1), dlopen'd lazily so normal builds/runs
carry no link-time or runtime dependency on libnvToolsExt.

Split out of Avarok-Cybersecurity#218 (DFlash speculative decoding) — purely additive
instrumentation, no behavior change to any existing code path.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant