-
Notifications
You must be signed in to change notification settings - Fork 282
perf(agentx): add LMCache offload arm to Kimi-K3 B300 at conc 56/70 #2802
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6831,3 +6831,14 @@ | |
| - "Use a 169 GB/rank HiCache target pool at c12 and c16 while retaining ratio mode for lower concurrencies." | ||
| - "Isolate SGLang runtime caches per Slurm allocation to prevent concurrent sweep cells from sharing per-rank cache files." | ||
| pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/2808 | ||
|
|
||
| - config-keys: | ||
| - kimik3-fp4-b300-vllm-agentic-dspark | ||
| scenario-type: | ||
| - agentic-coding | ||
| description: | ||
| - "Add an LMCache 0.5.5rc2 DRAM offload arm at concurrency 56 and 70, where the GPU prefix cache hit rate falls to 88.0% and 59.9%." | ||
| - "Size the LMCache chunk as block size x DCP size (1536 x 8 = 12288), required for chunking under decode context parallel." | ||
| - "Raise the LMCache L1 read-lock TTL to 3600s: the lock is held from prefetch to retrieve, and at concurrency 70 a queued request can exceed the 300s default, which fails the retrieve." | ||
| pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/2802 | ||
| append-only: true | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Append-only merges a new seriesMedium Severity The changelog marks this entry Reviewed by Cursor Bugbot for commit 83657b8. Configure here.
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch on the inconsistency — the PR body did say "kvdram-lmcache is a new visual series" in an earlier revision. That claim was wrong and has been removed; the body now states the opposite. To be precise about the mechanism: So the alternative implied here — publishing a separate LMCache series — is not reachable from the changelog flag; it would require changing the series keying repo-wide. What The distinct exp-names are still load-bearing — they keep the two arms as separate database points and separate result artifacts, which is what the concurrency overlap is for. They were never claimed to produce separate legend entries. |
||


There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LMCache install skips runtime deps
Medium Severity
lmcache==0.5.5rc2is installed with--no-deps, so declared runtime packages such ascupy-cuda13x,cuda-python, andsortedcontainersare not pulled in. Every other LMCache recipe in this repo that uses--no-depsinstalls those extras explicitly. The connector import check can pass whilelmcache serveror its GPU workers later fail on a missing module.Reviewed by Cursor Bugbot for commit a2bb1e2. Configure here.