Experiment: persistent evaluator for inline CUDA and Triton - #526
Draft
msaroufim wants to merge 3 commits into
Draft
Experiment: persistent evaluator for inline CUDA and Triton#526msaroufim wants to merge 3 commits into
msaroufim wants to merge 3 commits into
Conversation
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||
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.
KernelBot starts fresh Python processes for submission import and evaluation even inside a warm Modal function. This draft adds a reproducible experiment comparing that path with one persistent Python/CUDA worker behind
run_program. It supports the bundled inline-CUDA and Triton examples and preserves the existing correctness and timing function bodies.Inline CUDA saved 19–28% of total evaluation time with cold compilation caches. Four-submission batch results on T4:
In the complete repeat, median compile/import time was 31.74 → 29.85 seconds per submission, while the benchmark request dropped from 5.89 → 0.41 seconds. Compilation dominates the remaining time.
Kernel-score equivalence remains unresolved: reported kernel medians were 12–15% higher in persistent mode in the complete repeat. That ordered run does not isolate process state from clock/thermal drift or measurement variability. This needs investigation before ranked use.
Validation:
The production runner is unchanged. This is a trusted-example, single-GPU benchmark prototype without arbitrary-code isolation or production timeout/CUDA-fault recovery. Both experiment sandboxes are stopped.
Measured report and evidence · Reproduction and request flow
Draft for discussion and iteration. Do not merge.