multimodal local stack that feels real on GB200

[batchwire]

Did a bit of testing and thought I'd post the result here.

Short version: MLX behaved well for me, but only after I stopped ignoring reranking.

Happy to post more details if anyone wants them. At this point the real bottleneck is my patience.

[cobalttinker]

Did a bit of testing and thought I'd post the result here.

Tried to reproduce it just now. The issue went away once I changed one setting and restarted the stack cleanly. The main thing that moved was latency, not quality.

[audiopath66]

Did a small comparison this afternoon. On M3 Max with LM Studio, I saw basically the same behavior. The main thing that moved was latency, not quality.

[paperrunner]

Did a small comparison this afternoon. On M3 Max with LM Studio, I saw basically the same behavior. The main thing that moved was latency, not quality

What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at small local stacks. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.

[visionforge]

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. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it. I keep promising myself this is the last rebuild.

[cobalttinker]

A couple questions before I guess too hard. Is this local-only or are you routing anything externally?

[quietarch]

I tested this tonight. The issue went away once I changed one setting and restarted the stack cleanly.

[cobaltworks25]

I tested this tonight. The issue went away once I changed one setting and restarted the stack cleanly.

A couple things I'd check first. On 4090, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.

[cachelab]

I hit almost the same issue last night.

[thetaember38]

What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at tail latency.