[Autotuner] Add long-lived benchmark worker pool#2289
Closed
choijon5 wants to merge 1 commit into
Closed
Conversation
6a4339b to
45b1709
Compare
This was referenced May 5, 2026
45b1709 to
5103b79
Compare
023f042 to
39330c7
Compare
39330c7 to
2bcd8e4
Compare
stack-info: PR: #2289, branch: choijon5/stack/46
2bcd8e4 to
5a7590e
Compare
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.
Stacked PRs:
Add long-lived benchmark worker pool
splitting up this #2128 so that it's reviewable. This is extending the idea used for long lived processed during benchmarking (#2111) to precompilation. Each worker owns its own CUDA context and can be timed out, killed, and respawned independently, so CUDA sticky errors or hung jobs are contained to the worker instead of poisoning the autotune parent process.

Local benchmarking on H100 (run 3 times each) shows that the new mode, "pool", is faster than fork and on par in terms of perf.
Variance in perf and compile time is also slightly lower than fork:

This PR adds the low-level primitive needed by later PRs to parallelize autotune precompile/benchmark work while keeping CUDA failures isolated to worker processes.