0ba4cdb025
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.