[prototype] prioritized block soft pinning/evictions #17520
Closed
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.
built on top of #17519, this PR showcase a way to prioritized KV cache blocks by using the request priority flag. the usage is to keep a notion of priority in the free queue so some blocks are freed earlier than others, instead of a global LRU ordering.
see examples/experiments/offline-priority-prefix-caching.py and examples/experiments/online-priority-prefix-caching.py for usage. in short the request priority needs to be set as
priority:1or0. note we are just abusing the API here that this doesn't implement priority scheduling