Add 'mx.clear_cache()' to piecewise prompt processing in server.#917
Merged
Conversation
Contributor
|
It works! A single line of code with a mega impact. |
awni
approved these changes
Feb 23, 2026
Member
awni
left a comment
There was a problem hiding this comment.
Good catch! Not sure how we missed that.
Contributor
Author
|
Can we merge? |
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
3 participants
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.
Prompts that were being newly added to the server didn't have cache-clearing enabled while being processed. This lead to massive memory hang.
For prompts of length ~16K on GLM 4.7 Flash 6bit, this took peak memory from 50+GB to a more reasonable 28GB.