Scaling real-time STT for high-concurrency voice agents
Blog post from Gladia
Scaling real-time speech-to-text for high-concurrency voice agents requires treating persistent WebSocket streams as stateful sessions rather than applying stateless REST-style autoscaling. Key practices include routing sessions with affinity, scaling workers based on active connection counts instead of CPU alone, using ping/pong heartbeats and TCP keep-alives to remove hanging sessions, enforcing gateway connection limits, and monitoring p95 and p99 latency, queue depth, frame delays, and termination reasons. The discussion recommends realistic load testing with bursty arrivals, varied call durations, and representative audio, while identifying file descriptors, GPU memory, network behavior, inference capacity, and downstream LLM/TTS demand as possible bottlenecks. It also outlines approaches for managing overload, including pre-warming or snapshot restoration, selective buffering and frame dropping, admission control, circuit breakers, exponential-backoff retries, and multi-region routing for large deployments. The source contrasts self-hosted infrastructure, which requires capacity planning and operational management, with its managed Solaria-1 service, which it claims can add capacity automatically and provide low-latency partial and final transcripts.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| LLM | 21 | 1,189 | 251 | 109 | -83% |
| Real-time | 20 | 1,106 | 270 | 109 | -81% |
| Voice AI | 13 | 1,179 | 83 | 25 | -73% |
| Observability | 2 | 625 | 152 | 84 | -84% |
| Kubernetes | 1 | 634 | 79 | 44 | -75% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.