256 concurrent seqs risks OOM: worst case with long prompts in queue can exhaust KV cache + activation memory. 32K batched-tokens prefill activation ≈ 20GB competes with KV cache. 0.95 mem-util leaves only 5% headroom for spikes. Conservative start: max-num-seqs=8 (8× improvement over baseline=1). 8 seqs × 2048 avg context × 80KB/token = 1.3GB KV cache, safe. gpu-memory-utilization and max-num-batched-tokens restored to proven baseline values. Optimal max-num-seqs needs real-hardware sweep: 4→8→16→32→64→128. The value where Output TPS plateaus (KV cache saturated) is the answer. Can't determine this without Phanthy Cloud access.
35 lines
707 B
YAML
35 lines
707 B
YAML
concurrency: 1
|
|
command:
|
|
- python3
|
|
- -m
|
|
- vllm.entrypoints.openai.api_server
|
|
- --model
|
|
- /model
|
|
- --served-model-name
|
|
- llm
|
|
- --max-model-len
|
|
- '100000'
|
|
- --gpu-memory-utilization
|
|
- '0.9'
|
|
- --trust-remote-code
|
|
- -tp
|
|
- '4'
|
|
- --max-num-seqs
|
|
- '8'
|
|
- --disable-log-requests
|
|
- --disable-frontend-multiprocessing
|
|
- --max-num-batched-tokens
|
|
- '8192'
|
|
- --enable-chunked-prefill
|
|
- --max-seq-len-to-capture
|
|
- '32768'
|
|
- --enable-auto-tool-choice
|
|
- --tool-call-parser
|
|
- qwen3_coder
|
|
- --reasoning-parser
|
|
- qwen3
|
|
- --enable-prefix-caching
|
|
env:
|
|
- name: VLLM_ENGINE_ITERATION_TIMEOUT_S
|
|
value: 3600
|