Make the default max RAM cache size more conservative #7603
+13
−25
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.
Summary
This PR makes the default max RAM cache size slightly more conservative. This should help with some reports of Invoke using more RAM/VRAM than expected/desired. Of course, users always have the option to configure Invoke to use a larger cache size.
QA Instructions
The change is relatively straightforward. I tested the following cases:
Reviewers are encouraged to try this out on their systems to see if default performance is worse/better/the same.
The real test will be whether this reduces the number of issue reports with the default configs.
Merge Plan
No special instructions
Checklist
What's New
copy (if doing a release after this PR)