mirror of
https://github.com/kvcache-ai/Mooncake.git
synced 2026-11-05 01:17:55 +00:00
[GH-ISSUE #492] Support priority to evict the longer part of the prompt token list #171
Labels
No labels
ascend
auto-closed
bug
bug
CI/Build
Common
documentation
enhancement
feature request
good first issue
help wanted
high priority
MetaX
nightly-failure
pull-request
PyTorch Backend
question
RFC
Roadmap
stale
Store
Tests
Transfer Engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
kvcache-ai/Mooncake#171
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @maobaolong on GitHub (Jun 15, 2025).
Original GitHub issue: https://github.com/kvcache-ai/Mooncake/issues/492
It would be better, if we support evict the key(it is chunk in lmcache which contains a part of kvcache of prompt) which is the last tail chunk first.
If without this, we could evict the first n chunks first, then the following chunks of that prompt would never be used and become to garbage.
@ykwd commented on GitHub (Jun 16, 2025):
Hi, @maobaolong , glad to hear from you. Could you be more specific about the proposal?
@maobaolong commented on GitHub (Jul 12, 2025):
@ykwd Sorry the description is not complete before, I just finish it.
@ykwd commented on GitHub (Jul 14, 2025):
Thanks for the suggestion! We're currently preparing a series of optimizations around allocation and eviction.
As for prefix-aware eviction, I'm not yet sure what the optimal strategy would be. For example, regarding your idea of evicting from the tail of a prefix — one possible scenario is that the head KV entries of a prefix may already be cached locally (on device or host), while the tail entries are actually more likely to hit Mooncake.
@github-actions[bot] commented on GitHub (Jul 4, 2026):
This issue has had no activity for 90 days and will be closed in 7 days if there is no further activity. Please comment or react if it should stay open.
@github-actions[bot] commented on GitHub (Jul 12, 2026):
Closing due to 3 months of inactivity. If this is still relevant, please comment and we can reopen.