perf: cache MiniMax H3 text conditioning - #1966
Open
xledx wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Cache MiniMax H3 text-only conditioning results so repeated requests with the same prompt can reuse the previously computed
SDCondition.The cache is intentionally conservative and is only enabled when:
Non-cacheable H3 requests invalidate the cached condition.
Related Issue / Discussion
None.
Additional Information
Validated with MiniMax H3 on an Intel Mac, CPU-only, using
sd-serverso consecutive requests shared the same model context.On a repeated identical text-only request, the runtime log reported: