Allow cond to have more dynamo cache beyond limit #109318
Closed
Conversation
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
[ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/109318
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit f0bad33 with merge base 900288f ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
ydwu4
added
ciflow/trunk
This is short term workaround for #108500. In the long term, we should have separate caches if cond appears at different places in user code or per true_fn/false_fn cache. [ghstack-poisoned]
ezyang
approved these changes
Sep 15, 2023
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
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.
Stack from ghstack (oldest at bottom):
This is short term workaround for #108500. In the long term, we should have separate caches if cond appears at different places in user code or per true_fn/false_fn cache.
Test Plan:
see added test. It tests cond can go beyond cache limit.