NVIDIA Groq 3 LPX Hits 3,431 Tokens/sec on Long Context Benchmarks
NVIDIA's Groq 3 LPX, the interactive inference accelerator for the Vera Rubin platform, has posted its first third-party benchmark: 3,431 output tokens per second on Artificial Analysis's 100K context benchmark using the Gemma 4 31B model. This result targets the "high-interactivity" serving tier—the kind of responsiveness needed for multi-turn agentic sessions where context grows into the hundreds of thousands of tokens.
Why Long Context + Interactivity Is Hard
Agentic workloads are multiturn: each turn appends output to the context, and later turns must re-process everything that came before. At 100K+ input tokens, serving at 3,000+ tokens per second per user while managing a large KV cache is a systems challenge. The standard trick—tensor parallelism (TP)—splits computation across chips, but at the very small batch sizes required for interactive latency, the fixed cost of coordinating (collective ops) can eat the speedup.
The bottleneck is first-bit latency, not bandwidth. As the article states, with small tensors the transfer time is dominated by latency (A) rather than the amount of data (N) divided by bandwidth (B).
Groq 3 LPX's Approach
Groq 3 LPX solves this with deterministic, compiler-scheduled workload planning. The compiler pre-schedules when every tensor leaves and arrives, overlapping computation and communication at fine granularity. Preplanned chip-to-chip networking minimizes first-bit latency, making TP effective even at batch size 1.
On the SPEED-Bench, which measures agentic and coding-specific tasks, Groq 3 LPX hit a median of 4,767 output tokens per second. The system also supports multiple deployment configurations with Vera Rubin NVL72:
- Prefill-decode disaggregation
- Attention-FFN disaggregation
- Speculative external-drafter decoding
These can scale to multi-trillion parameter models, pairing Groq 3 LPX's interactivity with Vera Rubin's throughput for large-scale AI factories.
Who This Is For
Developers building agentic systems that demand high interactivity with long context—especially those running multi-agent workflows on 2T+ parameter models—will find this benchmark relevant to infrastructure planning.
📖 Read the full source: HN AI Agents
👀 See Also

Claude Opus 4.6 Breaks CLAUDE.md File References
Users report that Claude Opus 4.6 no longer automatically loads files referenced in CLAUDE.md, forcing manual intervention for each file.

The Orchestrator: Why Intent Should Outlive the Process
Current agent stacks invert identity and surface — the orchestrated layer should sit between agents and runtimes, with identity, routing, handoff primitives, and cross-driver calls. Practical example: triaging a flaky test across Ollama, Gemini CLI, and Grok Build under one intent.

Anthropic Launches Claude Partner Network with $100M Investment
Anthropic is launching the Claude Partner Network with an initial $100 million investment for 2026, providing training, technical support, and joint market development for organizations helping enterprises adopt Claude. Partners get access to technical certification, a Partner Portal with training materials, and a Code Modernization starter kit for legacy code migration.

Longitudinal study finds AI productivity gains at 10%, not 10x
A longitudinal study tracking 40 companies from November 2024 through February 2026 found AI usage increased by 65% on average, but pull request throughput only increased by 9.97%. The data suggests coding was never the primary bottleneck in software development.