Benchmarks
Whisper benchmarks. Audio hours per dollar.
Whisper large-v3 and large-v3-turbo on four rented GPUs, five setups: speed against real time, word error rate and what 1,000 hours of audio cost.
Measured
315xreal time
RTX 5090, faster-whisper large-v3-turbo, batch 16.
Run 2026-10-28
Whisper large-v3 audio hours per dollar. Five setups on four GPUs.
Batched faster-whisper with the turbo model transcribed 315 hours of audio per hour on the RTX 5090, about 267 hours of audio per dollar at the run-day price, at a 3.1% word error rate. Plain sequential large-v3 with beam search was 6.6x slower than the same weights batched on that GPU, with a higher error rate (5.7% against 3.2%).
Hardware
- RTX 5090 32 GB, L40S 48 GB, RTX A6000 48 GB and H100 PCIe 80 GB, one per machine, 6 to 20 vCPUs
Software
- faster-whisper BatchedInferencePipeline, batch 16: large-v3 fp16, large-v3 int8 (int8_float16), large-v3-turbo fp16
- transformers 4.57.1 pipeline, large-v3 fp16, 30 s chunks, batch 16, SDPA attention
- faster-whisper large-v3 fp16, plain model.transcribe, beam 5
Method
- distil-whisper/tedlium-long-form: 11 full TED talks, 8,905 s (2 h 28 min) of 16 kHz English with reference transcripts
- Wall time for all 11 talks after a one-minute warm-up (model load excluded), speed as a multiple of real time, word error rate with Whisper's English normalizer, peak GPU memory from nvidia-smi
What stood out
- int8 gave no speedup on any of the four GPUs. It saved about 1.8 GiB of memory and changed the error rate by 0.1 points at most.
- Turbo was 1.7 to 1.8x faster than large-v3 at the same error rate (3.1% against 3.2%) on this English set.
- The transformers pipeline had a 2.9% error rate, under every faster-whisper setup, at the highest cost per audio hour of the batched setups.
Keep in mind
- One English test set of TED talks: clean, single-speaker audio. Noisy calls, accents or other languages give different error rates.
- Peak memory comes from nvidia-smi, which includes what the frameworks reserve.
- The machines differ in CPU, disk and network (6 to 20 vCPUs), and the batched pipeline uses the CPU, so part of the GPU-to-GPU difference may come from the rest of the machine.
Costs
How the costs are worked out. Run day and today, side by side.
Run day
The cost the write-up printed: the hourly price the machine was launched at that day, against what it measured. Prices move daily, so each run-day figure carries its date. Every run was a single run.
Today
The run-day figure moved by today's price: the "from" price per GPU-hour shown on /pricing, over the run-day rate per GPU-hour. A GPU that is not in stock right now reads "Not in stock" rather than a stale price. Prices read 2026-11-04 04:00 UTC.
GPUs
The GPUs on this page. From price per GPU-hour, today.
Benchmarks