What problem does it solve?
When you launch an SGLang or vLLM serving instance, it is hard to tell where GPU HBM actually went or how many concurrent requests the deployment can sustain. This Skill parses startup logs to break memory into weights, KV pool, CUDA graph, framework overhead, and other categories, then estimates max concurrency for common token lengths.
Core Features & Use Cases
- Memory Decomposition: Extracts weight load, KV pool, CUDA graph, and framework overhead from SGLang and vLLM startup log lines, with per-category GiB, percentage, and derivation notes.
- Concurrency Estimation: Computes max concurrent requests from max_total_num_tokens and max_running_requests for token lengths like 4096, 6144, and 8192.
- Cross-Validation: Compares per-rank nvidia-smi readings against log-derived values and supports theoretical KV byte calculation from the model's config.json, including MLA and SWA/CSA/HCA attention variants.
- Use Case: After launching a DeepSeek model on 8xH200 with mem-fraction-static=0.88, run the analyzer on the startup log plus nvidia-smi output to see the KV pool budget, replication factor, and how many 8K-token requests can run concurrently before OOM.
Quick Start
Ask the agent to analyze your SGLang or vLLM startup log with the capacity analyzer, optionally providing nvidia-smi output and the model config.json, to get a memory breakdown and concurrency estimate.