Skip to main content
NVIDIA’s advanced Nemotron AI model showcasing 2.03x server throughput improvement, highlighting cutting-edge AI processing e

Editorial illustration for NVIDIA’s New Nemotron Model Achieves 2.03x Server Throughput

NVIDIA Nemotron Doubles Server Throughput with MoE

NVIDIA’s New Nemotron Model Achieves 2.03x Server Throughput

4 min read

NVIDIA's Nemotron-3-Super has a familiar problem: it's accurate, but it's a hybrid Mamba-Transformer MoE with 120.7B total and 12.8B active parameters, and that footprint eats into how many users a single node can actually serve at a decent token rate. The KV cache and Mamba state add up fast when you're running a big model at scale. NVIDIA's AI team went after that constraint directly with a new release called Nemotron-Labs-3-Puzzle-75B-A9B, a compressed version of Super built with the deployment target set before any architecture search happened.

Two goals drove the work: double the server throughput at 100 tokens per second per user, and get eight concurrent 1M-token requests running on a single H100. The result cuts the model down to 75.3B total and 9.3B active parameters while keeping the original 88-block hybrid layout intact. NVIDIA shipped three checkpoints on Hugging Face, in BF16, FP8, and NVFP4, and the paper lays out exactly what got trimmed inside those blocks, and at what cost to benchmark scores, to hit the throughput numbers in the headline.

Large hybrid MoE models like Nemotron-3-Super are accurate but expensive to serve. Their active parameters, KV cache, and Mamba state cap how many users a node can hold at a given per-user token rate. NVIDIA AI team has released Nemotron-Labs-3-Puzzle-75B-A9B, a compressed variant of Nemotron-3-Super.

Why this matters

Nemotron-Labs-3-Puzzle-75B-A9B is a useful data point for anyone budgeting GPU fleets rather than benchmark scores. Cutting active parameters from 12.8B to 9B while holding user throughput steady and gaining 2.03x server throughput tells us NVIDIA is optimizing for the metric that actually shows up on a cloud bill: how many concurrent users a single H100 node can serve at a given per-user token rate. The FP8 weights, FP8 KV cache, and FP32 Mamba state details matter here too, since memory, not compute, is what caps context length at 1M tokens on one H100 (70GB of 80GB HBM already gone to weights alone).

For teams building on hybrid MoE architectures, this is a reminder that "compressed variant of a larger model" is becoming its own product category, not just a quantization afterthought. If you're serving Nemotron-3-Super in production, the real question is whether Puzzle-75B-A9B's accuracy holds up closely enough to justify the throughput gain, and NVIDIA's own paper is the place to check that math before you swap models. Watch for third-party benchmarks confirming the accuracy trade-off.

Common Questions Answered

What is the key performance improvement of Nemotron-Labs-3-Puzzle-75B-A9B compared to Nemotron-3-Super?

Nemotron-Labs-3-Puzzle-75B-A9B achieves a 2.03x increase in server throughput while reducing active parameters from 12.8B to 9B. This compressed variant maintains user throughput steady while significantly improving how many concurrent users a single H100 node can serve at a given per-user token rate.

Why is the KV cache and Mamba state a constraint for serving large hybrid MoE models like Nemotron-3-Super?

The KV cache and Mamba state accumulate quickly when running large models at scale, which directly limits how many users a single node can serve while maintaining decent token rates. This memory footprint becomes a critical bottleneck for cloud deployment economics and GPU fleet budgeting.

What technical optimizations does Nemotron-Labs-3-Puzzle-75B-A9B use for efficient inference?

The model uses FP8 weights, FP8 KV cache, and FP32 Mamba state to optimize memory usage and computational efficiency. These precision choices allow the compressed variant to maintain accuracy while reducing the overall footprint required for deployment on hardware like H100 nodes.

How does NVIDIA's optimization of Nemotron-Labs-3-Puzzle-75B-A9B differ from traditional model benchmarking approaches?

Rather than focusing on benchmark scores, NVIDIA optimized for the metric that directly impacts cloud billing: concurrent users per node at a given per-user token rate. This practical approach prioritizes real-world deployment economics over abstract performance metrics.

LIVE11:50Governments Rush to Use AI for Cyber Defense Despite Risks