NVIDIAElizabeth GoodmanBenchmark
How Full-Stack NIM Optimizations Deliver 2.5x More Users on Nemotron 3 Ultra
Summary
Production serving for agentic AI must maximize concurrent users on fixed GPU infrastructure while preserving latency, especially with long prompts, reused context, and streamed responses. The article presents NVIDIA NIM as a deployable microservice that packages validated model- and GPU-aware choices, then measures Nemotron 3 Ultra NIM 2.0.12 against an open-source baseline on four B200 GPUs using a 64K/400 workload, 76% KV reuse, and 50 TPS per user (20 ms ITL). The optimized stack combines autotuned MoE and Mamba kernels, tensor and expert-aware parallelism, prefix and Mamba state-cache reuse, scheduling, batching, memory tuning, and MTP speculative decoding. At the stated target, throughput rises from 718 to 1,997 output tokens per second—more than 2.5x—while the article recommends replaying representative traffic with NVIDIA AIPerf to select a Pareto point meeting the application’s latency constraint.
Context
Production teams need to serve as many concurrent users as possible on available GPU infrastructure while preserving interactive latency. This tradeoff is especially important for agentic workloads with long prompts, reusable context, and extended streamed responses.
Approach / What changed
NVIDIA NIM packages validated model- and GPU-aware serving configurations into a deployable microservice. The Nemotron 3 Ultra NIM 2.0.12 stack combines autotuned MoE and Mamba kernels, tensor and expert-aware parallelism, prefix and model-state reuse, scheduler, batching and memory tuning, and MTP speculative decoding. The article also recommends benchmarking representative traffic with NVIDIA AIPerf and choosing a Pareto point that meets the application’s latency target.
Takeaways
On a four-B200 system at 50 TPS per user, the NIM-on configuration produced 1,997 output tokens per second versus 718 for the NIM-off baseline, exceeding 2.5x the baseline throughput.
The reported gains come from interacting optimization bundles rather than independently additive switches, including partial-prefix matching, Mamba state-cache settings, batching, memory allocation, parallelism, and MTP speculative decoding.
Published curves are a starting point rather than a universal guarantee; representative traffic should be replayed with pinned NIM versions and NVIDIA AIPerf to select a latency-compliant Pareto point.
Source and freshness
- Source
- developer.nvidia.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.