-
-
Notifications
You must be signed in to change notification settings - Fork 11.9k
Add config flag for VLLM_DISABLE_COMPILE_CACHE #30108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
elizabetht
wants to merge
11
commits into
vllm-project:main
Choose a base branch
from
elizabetht:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+121
−5
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
1f3411a
Add config flag for VLLM_DISABLE_COMPILE_CACHE
elizabetht 219558c
Add missing test for for VLLM_DISABLE_COMPILE_CACHE
elizabetht 64de3b1
Update docs
elizabetht fb438f3
Refactor tests
elizabetht d06d6c4
Keep custom cache flag out of inductor config patch
elizabetht c884f4b
Merge branch 'main' into feat/add-config-flag-for-disable-compile-flag
elizabetht 2157555
pre-commit checks
elizabetht 0acf712
Rebase
elizabetht b408d34
Fix PR comments
elizabetht 08ed479
Merge branch 'vllm-project:main' into main
elizabetht c779322
Merge branch 'vllm-project:main' into main
elizabetht File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Btw, positive flags are generally better than negative flags. Something like
enable_compile_cache. Because double negation gets confusing.I know the envvar is already negative, but we should (in the future) add a positive envvar and then deprecate the negative envvar. In that sense, I'd prefer that we have the config flag be positive.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zou3519 I agree that positive flags are clearer than negative ones.
In this PR I mirrored the existing env var naming to keep behavior and terminology aligned with what’s already shipped. The original issue was specifically “add a config flag for the existing env var,” so I followed the same pattern here.
I’d prefer to handle the rename as a follow-up: introduce a positive config flag and env var, then deprecate the negative env var in a controlled way. Otherwise this PR ends up mixing “add config flag” with a behavioral/UX change.
If you’d still like the positive flag in this PR, I can update it, but my inclination is to track that as a separate issue and keep this change scoped to exposing the current env var via config.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Renames require deprecation etc, so if we're planning to rename something we should just name it right the first time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ProExpertProg Just to clarify your suggestion: are you proposing that the config flag be renamed to
enable_compile_cacheinstead? I may be misunderstanding the intent of your comment - could you elaborate a bit on what you’d like the flag to be called? My concern is that env var (which will be present still) will be VLLM_DISABLE_COMPILE_CACHE and config flag will beenable_compile_cache. Am I missing something?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't want to introduce a negative flag and then have to deprecate the negative flag. This PR can introduce both the positive flag and a positive envvar, if your worry is consistency. Then we can deprecate the negative envvar.