Skip to content

workload: add guide_p2p-kv-cache-sharing_1 profile (document Q&A)#1656

Draft
nilig wants to merge 4 commits into
llm-d:mainfrom
nilig:feat/p2p-guide-profile
Draft

workload: add guide_p2p-kv-cache-sharing_1 profile (document Q&A)#1656
nilig wants to merge 4 commits into
llm-d:mainfrom
nilig:feat/p2p-guide-profile

Conversation

@nilig

@nilig nilig commented Jul 17, 2026

Copy link
Copy Markdown

Part of llm-d/llm-d#2066 (companion to llm-d/llm-d#2067).

Dedicated inference-perf profile for the p2p-kv-cache-sharing guide's headline benchmark: 192 conversations with 48K-token private document prefixes, 6 short Q&A turns each, 128 concurrent. Sized so the corpus oversubscribes a 14-16 pod H200 fleet's aggregate GPU KV; the profile documents scaling num_conversations to other fleets. The guide's benchmarking README references this profile in its run instructions.

Dedicated inference-perf profile for the p2p-kv-cache-sharing guide's
headline benchmark: 192 conversations with 48K-token private document
prefixes, 6 short Q&A turns each, 128 concurrent. Sized so the corpus
oversubscribes a 14-16 pod H200 fleet's aggregate GPU KV; scale
num_conversations to the target fleet.

Signed-off-by: nilig <nili.ifergan@gmail.com>
nilig added 3 commits July 24, 2026 17:32
The --spec guides/p2p-kv-cache-sharing entry point and the scenario it
references complete the per-guide file set alongside the workload
profile. The scenario deploys via the upstream guide's own manifests
(kustomize mode), so the stack definition is not mirrored here.

Signed-off-by: nilig <nili.ifergan@gmail.com>
A fresh capacity measurement on the guide's pinned config put per-pod
GPU KV at ~1.22M tokens, not the ~0.48M this comment assumed - at the
corrected figure the 9.2M-token corpus fits inside the fleet's
aggregate GPU cache, so what drives placement here is per-pod queueing
under concurrency, not corpus size versus aggregate capacity. See
llm-d#2067 for the corresponding guide/report fix.

Signed-off-by: nilig <nili.ifergan@gmail.com>
…load profile

Matches the guide benchmark report's uniform-pool parameters: 128
shared 48K-token prefixes, 256-token questions, 64-token outputs,
constant-rate stages 4-24 req/s. Completes the guide's dedicated
profile set alongside the docQA headline profile.

Signed-off-by: nilig <nili.ifergan@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant