hybrid retrieval results: what are you seeing?

[sanescope]

Spent some time on this today and wanted to compare notes.

I'm comparing two approaches here: keep it simple on mini PC, or squeeze more out of the stack and deal with the complexity.

What would you pick if you had to live with it for a few months?

For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.

[homelabhenry]

Spent some time on this today and wanted to compare notes.

I'd approach it in a boring order. 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.

[bytelab]

Did a small comparison this afternoon. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed.

[orbitgarden]

Need a little more detail here. Are you testing this on GB200 or something else?

[routeforge64]

Thanks, that helps. I ended up in about the same place using Ollama.

[bytelab]

What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with FLUX and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.

[emberquill]

Interesting, I hadn't tried that. That matches what I saw on 7900 XTX.

[labpath]

Did a small comparison this afternoon. My result was mixed: first run looked bad, second run looked normal.

[modbench]

Appreciate the detail. That matches what I saw on M3 Max. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.