Repository navigation
feat: extend CUDA parity matrix and public-operation diagnostics - #2
Merged
Merged
Conversation
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.
Extend the CUDA migration benchmark harness beyond isolated kernel timings so migrations can be checked against CPU behavior, historical RawKernel implementations, and completed public operations. The initial harness was merged in #1; these are the subsequent additions on this branch.
Instrumentation is kept separate from unprofiled timings. CUDA-event intervals include host submission gaps and are not labeled pure device execution time. The comprehensive matrix does not claim exhaustive public API coverage or substitute for Nsight synchronization/allocation measurements; coverage gaps are explicit.
Validation: 194 local tests passed for this revision; batch scripts passed syntax checks. Della runs have exercised public-operation comparisons and diagnostics. The latest public ListArray result (run 16325085) passes every candidate case while exposing missing historical-baseline jagged bounds errors. A direct before/after comparison of the latest Awkward jagged scratch optimization is still queued; no performance benefit from that optimization is claimed here.
Related upstream work: scikit-hep/awkward#4481, scikit-hep/awkward#4483 and scikit-hep/awkward#4484. Results describe measured revisions, not a blanket performance claim for all migrations.
AI assistance was used to implement, test and document this contribution.