Inference
Audio / Speech discussion - Printable Version

+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Generative AI (https://www.datasculpting.ai/inference/forumdisplay.php?fid=17)
+--- Forum: Audio / Speech (https://www.datasculpting.ai/inference/forumdisplay.php?fid=71)
+--- Thread: Audio / Speech discussion (/showthread.php?tid=827)



Audio / Speech discussion - vramport - 10-06-2026

This keeps coming up in conversation so I figured I'd start a thread.

One thing I keep noticing is that people underestimate HBM constraints until they actually try to run this stuff for more than one afternoon.

Curious whether that lines up with what other people are seeing.


Re: Audio / Speech discussion - sparrowhall - 10-07-2026

Can you fill in a bit more context? What model, what runtime, and roughly what context size?


Re: Audio / Speech discussion - macrostack69 - 10-07-2026

Not sure I agree there. I've seen people blame prefill/decode split when the real issue was much more mundane. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.


Re: Audio / Speech discussion - vectorfield - 10-08-2026

Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed.


Re: Audio / Speech discussion - signalcraft14 - 10-08-2026

Appreciate the detail. I ended up in about the same place using TensorRT-LLM. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.


Re: Audio / Speech discussion - bytesupply76 - 10-08-2026

same here on my side.


Re: Audio / Speech discussion - vectorfield - 10-09-2026

I'd approach it in a boring order. On A6000, the easiest win is often to back off the aggressive settings and see whether the problem survives. Once you know the plain path works, then add the faster path back in piece by piece.


Re: Audio / Speech discussion - cozywire - 10-09-2026

Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly.