A 50 ms check was burning a second of CPU
A voice check on my calls looked cheap on the stopwatch and cost twenty times more in CPU. The cause was 23 idle OpenBLAS threads spinning while a different library did the work.
A voice check on my calls looked cheap on the stopwatch and cost twenty times more in CPU. The cause was 23 idle OpenBLAS threads spinning while a different library did the work.
Two calls went dead in one morning. My first diagnosis matched the clock to the second and was wrong. The real cause was one bare await on a shared asyncio future.