where reranking mattered

[kernelghost]

Thought I'd post a small recipe because a lot of threads ask similar things.

Maybe useful as a starting point: MLX on GB200, keeping HBM constraints in mind from the start.

If someone wants the exact settings I can clean them up and post them.

My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.

[modrunner27]

A couple things I'd check first. On 7900 XTX, 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.

[homelabhenry]

That matches what I was seeing. I don't think your conclusion is far off. The biggest change for me was simplifying the stack instead of adding one more optimization layer. I keep promising myself this is the last rebuild.

[deltastation]

Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal.

[tinycontext]

worth checking the driver first.

[quietsupply11]

I think the bottleneck is somewhere else. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Could be a workload difference, but I wouldn't generalize too fast from one setup.

If you post your exact settings, people here can probably narrow it down pretty fast.

[bytelab]

That matches what I was seeing. The pattern around embeddings has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. At this point the real bottleneck is my patience.

[phasenode]

My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at small local stacks.

[turbogrid11]

Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?

[homelabhenry]

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