Back to workloads

Model card / Full duplex voice

Model by NVIDIA

Nemotron VoiceChat 11B

Wave serves the complete speech-in, speech-out model as one continuous GPU program. The highest tested profile keeps 56 independent conversations on time on one H100.

Two Renaissance scholars wearing blue in a dark stone workshop.
Measured

56

Real-time conversations

Per H100 SXM 80 GB. Highest session count tested.

Measured

147.5ms

Worst server-boundary p99

Across three runs, against a 160 ms serving deadline.

Measured

0

Late beats

Out of 84,000 measured beats at 56 simultaneous sessions.

Nemotron VoiceChat listens, reasons and speaks continuously. Serving it means advancing every active conversation before the next audio arrives—not simply maximizing tokens per second.

The serving envelope

.wave runs the full five-model pipeline through WPK (Wave Persistent Kernel), its persistent GPU kernel, and advances a fixed cohort together. At 56 conversations, its worst p99 across three runs was 147.5 ms, leaving 12.5 ms inside the 160 ms beat.

WPK and the reference serving stack plotted by concurrent conversations on a linear axis and speed relative to their real-time deadline on a logarithmic axis.
Higher is better; 1× means the serving deadline is just met. Session count is linear and speed is logarithmic. WPK at 48 and 56 sessions is measured; lower counts are estimated. The physical ceiling is modeled.

Measured results

The comparison holds the checkpoint, input, context, hardware and precision fixed. Each point below reports the range across three consecutive runs.

Server-boundary p99 per beat and observed late beats.
SystemSessionsp99Late beats
.wave48139.9–140.0 ms0 / 72,000
.wave56147.4–147.5 ms0 / 84,000
Reference NIM · two-step1142–143 ms1 / 1,500
Reference NIM · two-step2172–176 ms8–15%
Reference NIM · two-step4186–188 ms26–39%
Reference NIM · two-step8317–351 msMost

What was held constant

Both engines load the same 1,629 tensors and use the same model precision. Every session receives the same recorded question after 40 seconds of silence, followed by an 80-second scored window and an 8-second tail.

Measurement conditions
  • Two causal 80 ms model steps per 160 ms serving beat.
  • About two minutes of accumulated context at the end of the scored window.
  • BF16 perception and backbone; FP32 recurrent state, speech generation, codec and recognition; TF32 matrix multiplies.
  • Three consecutive runs per measured point, with every failed attempt retained and counted.
  • Timing at each server boundary. .wave includes its data plane; the reference measurement bypasses the NIM WebSocket service and measures its Triton boundary.

The recorded workload checks the exact user transcript and nonempty assistant audio. It does not by itself establish broad conversational quality across every speaker, language or long-running production condition.

Machine-readable serving profile

Working on a streaming model?

Tell us about your model, expected traffic and timing requirements.

Talk to an engineer