Skip to content
exExperimentos
← Lab Notes
Free13 Oct 2026 · 1 min read

Keeping FP32 and moving Supertonic to Triton

Rather than reduce the CPU graph precision again, this follow-up used NVIDIA Triton’s ONNX backend with CUDA execution and the unchanged FP32 graphs. The paired comparison retained both speed and acoustic checks.

A different optimization

Rather than reduce the CPU graph precision again, this follow-up used NVIDIA Triton’s ONNX backend with CUDA execution and the unchanged FP32 graphs. The paired comparison retained both speed and acoustic checks.

Faster first audio

English median TTFT changed from 1.154 seconds on CPU to 0.349 on the GPU route. Spanish changed from 1.079 to 0.341. Median RTF changed from 0.353 to 0.109 and from 0.345 to 0.107. Measured WER matched within each language, and waveform correlation exceeded 0.9994. The route used about 989 MiB of GPU memory.

Check the deployed path separately

A later forty-eight-request production API check passed. English TTFT was about 341 ms with RTF 0.110 and WER 3.57%; Spanish about 340 ms, RTF 0.107 and WER 3.09%. These numbers should not be pooled with the earlier paired corpus.

Synthetic two-way server exercises combining ASR, translation and synthesis passed with about 0.92/0.82 seconds of server turnaround. The physical phone was installed but locked, so this does not prove microphone capture, international network delay or real two-phone conversation acceptance.

Evidence and publication boundary

This is an edited account of the recorded experiment. The linked archive is private; the methods, aggregate findings and limits are included above. Reference recordings, raw conversations, authentication material and workstation configuration are excluded.

Source: tts/supertonic3-precision-triton-2026-10-13/triton/REPORT.md

Free Lab Notes

Follow the next experiment

Get new findings in your feed reader. All published articles and measurement exports are free to read.

Follow via RSS