
If you're serving million-- workloads, this breaks down the real bottlenecks — compressed layouts, prefix caching, and kernel maturity on HGX B200 — so you can pick endpoint profiles and reason about long-context cost/latency instead of treating context length as a free model feature.
“Benchmark tables miss the main point of DeepSeek-V4: the important change is architectural. V4 turns million-token context into a serving-systems problem.”
Together AI
“A full-SWA implementation actually had a higher per-token KV footprint than our V3 path — roughly 3.8 KB per token versus 3.4 KB — because the engine was storing the full sliding-window state.”
Together AI
“By keeping only the SWA states most likely to be reused, we increased total KV-cache capacity on a single NVIDIA HGX B200 node from roughly 1.2M tokens to 3.7M tokens with minimal changes.”
Together AI
“Heavily Compressed Attention (HCA) uses the same compression idea but with stride 128. At a 1M-token context length, that reduces the cache from 1M token positions to roughly 8K compressed entries.”
Together AI
“For these workloads, the cost model often shifts from price per token toward cost per completed trajectory.”
Together AI
Checking sign-in…
Loading comments…