mirror of
https://github.com/kvcache-ai/Mooncake.git
synced 2026-11-05 01:17:55 +00:00
[GH-ISSUE #2] Inquiry Regarding Prefix Caching in the vllm Baseline #2
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#2
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 @Lin-Qingyang-Alec on GitHub (Jul 27, 2024).
Original GitHub issue: https://github.com/kvcache-ai/Mooncake/issues/2
I hope this message finds you well. I recently read your technical report, and I found it very insightful. Thank you for sharing your work!
While reviewing the experimental details, I noticed some aspects related to the baseline were not entirely clear. Specifically, you mentioned using the vllm service as a baseline for Mooncake. I observed that Mooncake utilizes prefix caching technology, and I noticed that vllm has a startup parameter: --enable-prefix-caching, which seems to serve a similar purpose.
Could you kindly clarify whether you enabled this feature in the baseline during your experiments?
Thank you for your time, and I appreciate any insights you can provide.
Best regards.
@james0zan commented on GitHub (Aug 1, 2024):
The support of prefix cache in vLLM is later than our experiment thus we do not compare with it.
@github-actions[bot] commented on GitHub (Jul 25, 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 (Aug 2, 2026):
Closing due to 3 months of inactivity. If this is still relevant, please comment and we can reopen.
MemcpyWorkerPool::workerThreadunder TCP transport with concurrent put/get #551