NVIDIA Developer Blog · · 8 min read

How Full-Stack NIM Optimizations Deliver 2.5x More Users on Nemotron 3 Ultra

Mirrored from NVIDIA Developer Blog for archival readability. Support the source by reading on the original site.

How Full-Stack NIM Optimizations Deliver 2.5x More Users on Nemotron 3 Ultra

How full-stack serving optimizations increase user capacity on a 4xB200 system at a concrete interactivity target

AI-Generated Summary

  • Nemotron 3 Ultra NIM delivers up to 2.5x higher system throughput on a 4xB200 system compared with a baseline serving stack without NIM optimizations.
  • The NIM 2.0.12 optimized serving stack combines autotuned kernels, tensor parallelism, prefix and state reuse, scheduler and memory tuning, and MTP speculative decoding to achieve 1,997 tokens per second at a 50 TPS per user target.
  • NIM packages model- and GPU-aware serving choices into a deployable microservice with validated configurations, standard APIs, and an enterprise-ready container lifecycle through NVIDIA AI Enterprise.
  • Developers can benchmark the NIM against their own traffic using NVIDIA AIPerf to replay representative workloads and select the Pareto point that meets their latency SLO.

Next Steps

Powered by NVIDIA Nemotron. AI-generated content may summarize information incompletely. Verify important information. Learn more

Deploying a large language model is only the first step toward production-ready serving. Production teams also need to serve as many concurrent users as possible on available GPU infrastructure while preserving the interactivity that keeps applications responsive.

That tradeoff matters even more for agentic AI workloads, where prompts can be long, context can be reused across steps, and applications often stream extended responses back to users.

NVIDIA NIM packages model- and GPU-aware serving choices into a deployable microservice. Instead of starting from a blank runtime configuration, developers get a validated serving configuration and a supported deployment path, while retaining the ability to benchmark the NIM against their own traffic.

What NIM adds: Performance engineering and production readiness

Inference performance is a system property. Precision and kernels, parallelism, scheduling, batching, memory allocation, prefix reuse, model-specific state caches, and decoding strategy all interact. A configuration is useful only if it improves throughput while staying within the application latency target.

NIM turns this optimization work into a tested starting point. NVIDIA engineers validate configurations for supported model, GPU, and precision combinations, then package the runtime and model artifacts behind standard APIs. For production deployments, NIM Certified adds regular inference-stack updates, CVE handling, broader hardware validation, and commercial support through NVIDIA AI Enterprise.

NIM delivers two benefits in one deployment path: validated performance engineering plus an enterprise-ready container lifecycle and support model.

Case study: Nemotron 3 Ultra NIM delivers up to 2.5x higher throughput for agentic workloads

The benchmark definition used throughout this article is:

  • Hardware: 4xB200
  • Agentic workload: 64K/400/76% KV reuse/50 TPS/user (20 ms ITL)

This Pareto chart compares the open-source baseline serving stack (NIM Off) against the fully optimized NIM 2.0.12 serving stack (NIM On).

Line chart showing two Pareto curves for Nemotron 3 Ultra NIM on a 4xB200 system. The x-axis is interactivity in tokens per second per user (0-450); the y-axis is total system output-token throughput in TPS (0-2,500). The NIM-off curve (blue) plateaus around 750 TPS and drops steeply. The NIM-on curve (green) reaches approximately 2,000 TPS at 50 TPS/user and sustains higher throughput across the full interactivity range. An annotation at 50 TPS/user shows a 2.5x gap between the two curves.
Figure 1. Pareto curve for Nemotron 3 Ultra NIM on a 4xB200 system, with NIM optimizations off and on. At 50 TPS/user, the NIM-on curve delivers more than 2.5x the system throughput of the baseline, translating directly into more concurrent users at the same interactivity
ConfigurationNative 256K max contextWhat it represents
NIM Off baseline718 tok/sNo NIM optimizations
NIM On (2.0.12) optimized serving stack1,997 tok/s 2.5x v. BaselineOptimized NIM stack: cache/state reuse, MTP speculative decoding and associated fixes, autotuned kernels, partial-prefix matching, scheduler, batching, memory, and parallelism tuning
Table 1. System output-token throughput across four B200 GPUs at the 50 TPS/User target

How NIM 2.0.12 optimized serving stack works

The measured gains come from interacting configuration bundles, not independent switches whose percentages can simply be added. The main optimization layers are:

  • Precision and autotuned model-aware kernels. Autotuned mixture-of-experts and Mamba kernels map the hybrid architecture efficiently to NVIDIA Blackwell GPUs.
  • Parallel execution. Tensor parallelism distributes the model across four GPUs, while expert-aware execution improves utilization for the mixture-of-experts layers.
  • Prefix and model-state reuse. Prefix caching avoids recomputing repeated context, partial-prefix matching recovers reuse when only part of a prefix matches, and Mamba state-cache settings are tuned for the model architecture.
  • Scheduler, batching, and memory tuning. Concurrent-sequence limits, batched-token limits, block size, and GPU-memory allocation keep more work in flight without crossing the latency target.
  • MTP speculative decoding. NIM 2.0.12 optimized serving stack (including MTP) adds MTP and its associated fixes to the same optimized serving stack. The incremental benefit depends on acceptance rate and available memory headroom.

Benchmark the NIM on your own workload

The published curves are a starting point, not a promise that every application will see the same result. The fastest way to determine fit is to replay representative traffic and build a Pareto curve for the latency metric that matters to your users.

  • Deploy the exact software versions. Use NIM 2.0.12 (or newer version), and pin the image tag or digest for every run.
  • Prepare representative traffic. Use a Mooncake-format JSONL trace or capture controlled NIM requests, with appropriate access controls and sanitization for sensitive data.
  • Measure performance. Use NVIDIA AIPerf to replay representative traffic and get perf benchmarks
  • Select the Pareto point that meets the SLO. Compare output throughput among points that satisfy the SLO/latency constraints and determine fit for deployment:
for C in 1 4 8 16 32 64; do
   aiperf profile \
 	--model nvidia/nemotron-3-ultra-550b-a55b \
 	--endpoint-type chat --streaming \
 	--url localhost:8000 \
 	--input-file ./agentic-trace.jsonl \
 	--custom-dataset-type mooncake_trace \
 	--no-fixed-schedule \
 	--concurrency "$C"
 done

Example AIPerf concurrency sweep. Replace the trace, request count, and endpoint details with the workload you want to model.

Download and run Nemotron 3 Ultra NIM

Start from the Nemotron 3 Ultra NIM page, accept the governing terms, and select the NIM 2.0.12 tag or the exact published digest. After downloading, find and select a profile. The following lists all profiles packaged in the NIM:

 export NGC_API_KEY=<your-personal-api-key>
 export LOCAL_NIM_CACHE=$HOME/.cache/nim
 export NIM_TAG=2.0.12
 mkdir -p "$LOCAL_NIM_CACHE"
 echo "$NGC_API_KEY" | docker login nvcr.io \
   --username '$oauthtoken' --password-stdin
 docker run --gpus all --shm-size=16GB \
   -e NGC_API_KEY \
   -e NIM_MODEL_PROFILE \
   -v "$LOCAL_NIM_CACHE:/opt/nim/.cache" \
   -p 8000:8000 \
   nvcr.io/nim/nvidia/nemotron-3-ultra-550b-a55b:$NIM_TAG list-model-profiles

To pick an optimized profile for agentic workloads on a four-GPU B200 system, you would set the NIM_MODEL_PROFILE to vllm-nvidia-b200-nvfp4-tp4-pp1-throughput-90.0 and enable speculative decoding:

 export NGC_API_KEY=<your-personal-api-key>
 export LOCAL_NIM_CACHE=$HOME/.cache/nim
 export NIM_TAG=2.0.12
 export NIM_MODEL_PROFILE=vllm-nvidia-b200-nvfp4-tp4-pp1-throughput-90.0
 mkdir -p "$LOCAL_NIM_CACHE"
 echo "$NGC_API_KEY" | docker login nvcr.io \
   --username '$oauthtoken' --password-stdin
 docker run --gpus all --shm-size=16GB \
   -e NGC_API_KEY \
   -e NIM_MODEL_PROFILE \
   -e NIM_SPECDEC_ENABLE=1 \
   -v "$LOCAL_NIM_CACHE:/opt/nim/.cache" \
   -p 8000:8000 \
   nvcr.io/nim/nvidia/nemotron-3-ultra-550b-a55b:$NIM_TAG

A performance-engineered starting point for production

NVIDIA NIM packages model- and GPU-aware serving optimizations into a deployable microservice. For Nemotron 3 Ultra on a 4xB200 system, these optimizations let organizations serve up to 2.5x more users at 50 TPS/user compared with a NIM-off baseline, while keeping the deployment path practical for real multi-user serving.

NIM combines validated performance engineering with regular inference-stack updates, CVE handling, hardware validation, and commercial support through NVIDIA AI Enterprise. More performance-optimized NIM configurations are planned across a broader range of models, giving developers additional validated starting points for their own latency, throughput, and cost objectives.

Get started

Download the Nemotron 3 Ultra NIM 2.0.12 from NGC, run it on your NVIDIA GPU infrastructure, and replay representative traffic with NVIDIA AIPerf to select the Pareto point that meets your application target.

Resources

Discuss (0)

Tags

Agentic AI / Generative AI | Developer Tools & Techniques | General | Nemotron | NIM | Intermediate Technical | Deep dive | Build AI Agents | Inference Performance

About the Authors

Avatar photo
About Arun Venkatesan
Arun Venkatesan is a group product manager on the AI Inference team at NVIDIA. He previously led NVIDIA’s Speech AI product team. Before joining NVIDIA, Arun held engineering leadership roles and built conversational AI applications, as well as enterprise and consumer software products. He earned an MBA from the Yale School of Management and a Master’s degree in Electrical and Computer Engineering from the University of Maryland, College Park.
Avatar photo
About Chintan Patel
Chintan Patel is a senior product manager at NVIDIA focused on bringing GPU-accelerated solutions to the HPC community. He leads the management and offering of the HPC application containers on the NVIDIA GPU Cloud registry. Prior to NVIDIA, he held product management, marketing and engineering positions at Micrel, Inc. He holds an MBA from Santa Clara University and a bachelor's degree in electrical engineering and computer science from UC Berkeley.
Avatar photo
About Adam Shaver
Adam Shaver is a senior engineer in NVIDIA Inference Microservices (NIM) with a primary interest is in improving performance across the NIM catalog. In the world of software, Adam uses his MSc of Cybernetics (University of Reading, UK) to model systems, reduce complexity, and build self-reinforcing solutions.
Avatar photo
About Sungsoo Ha
Sungsoo Ha is a senior deep learning algorithm engineer at NVIDIA, where he works on inference optimization for LLMs. His primary technology interests are disaggregated serving, long-context decoding, and GPU parallelism strategies. He delivers NVIDIA Dynamo inference recipes and contributed decode context parallelism to vLLM and SGLang. Before NVIDIA, he optimized runtime inference for the code-editing model behind Amazon Q Developer at AWS. Sungsoo holds a PhD in Computer Science from StonyBrook University.

Comments

Discussion (0)

Sign in to join the discussion. Free account, 30 seconds — email code or GitHub.

Sign in →

No comments yet. Sign in and be the first to say something.

More from NVIDIA Developer Blog