Compile Python load_inline submissions on CPU before Modal GPU evaluation - #528
Merged
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.
Python submissions that compile with
load_inlinecurrently hold a GPU while the compiler runs. The Modal launcher now first imports those submissions in a CPU worker, transfers the compiled extensions, and reuses matching libraries during GPU evaluation. Users keep their existingsubmission.pyandload_inlinecalls.CPU import errors, timeouts, unsupported builds, and mismatched sources, flags, ABI, image, or header dependencies fall back to normal GPU compilation. Other Python submissions use the existing GPU path. The evaluator and correctness decisions are unchanged. Workers share the runner image and read-only PCH Volume; CPU containers are single-use with restricted Modal access. Artifacts are scoped to one request and limited to 1 MiB compressed.
KERNELBOT_CPU_COMPILE=0disables the CPU attempt.Validation:
The guide includes the local debug command, supported scope, and rollout instructions. Production has not been deployed.