Scope DeepCompile compiler state to engine lifecycles#8159
Draft
tohtana wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Masahiro Tanaka <mtanaka@anyscale.com>
tohtana
force-pushed
the
tohtana/deepcompile-compiler-lifecycle-standalone
branch
from
July 23, 2026 01:01
0b27f37 to
8f8f693
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.
Problem
Scheduler-planned recompilation resets Dynamo and replaces compiled graphs. DeepCompile's forward inputs, compiled-backward frames, and process-global compiler configuration and constructor patch need explicit lifecycle ownership so prior graph state can be released without disturbing another engine.
Approach
AotAutograd.__init__patch restorable and ownership-safe.Testing