netrunner(@plotarmordev):If that Nemotron Transcribe speed number was measured with lots of streams running at once, it's a batch number. Good for chewing through an archive of recordings, much less useful for a voice agent. Running many streams together keeps the GPU busy and pushes total throughput up, even if each single stream waits longer. A voice agent is one stream with a person waiting on the other end. The number we should focus on is time to first words at concurrency 1 imo

2026.10.30 04:46

If that Nemotron Transcribe speed number was measured with lots of streams running at once, it's a batch number. Good for chewing through an archive of recordings, much less useful for a voice agent. Running many streams together keeps the GPU busy and pushes total throughput up, even if each single stream waits longer. A voice agent is one stream with a person waiting on the other end. The number we should focus on is time to first words at concurrency 1 imo

Artificial Analysis@ArtificialAnlys

2026.10.28 15:05

To measure speed and cost efficiency, we benchmarked Nemotron 3.5 Transcribe on DeepInfra's hosted endpoint. On DeepInfra, it reaches a Speed Factor of 75x, transcribing 1 minute of audio in under 1 second, and costs $2.00 per 1,000 minutes of audio.