small speech stack for local use: anyone testing this?

[amberpatch25]

A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at structured output. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.

[quiethouse]

That matches what I was seeing. The pattern around router policy has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.

[vectorfield]

I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed.

[vramarch]

What worked for me was pretty simple. If you're on MLX, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.

[quantyard]

That matches what I was seeing. That matches what I saw on 4090. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.

[kernelpeak]

What worked for me was pretty simple. If you're on MLX, I'd confirm the version first and then reduce variables until the behavior is obvious.