when RAG was overkill

[southtinker]

Posting this in case it saves someone else a little time.

If you were starting from scratch today for this use case, what would you choose first and what would you ignore?

Would rather learn from your scars than collect my own all at once.

[kernelmike]

I don't think that's the whole story. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Worth testing the simpler explanation before adopting the more interesting one.

[macropilot]

I think the bottleneck is somewhere else. I've seen people blame prefill/decode split when the real issue was much more mundane.

[batchsize]

Thanks, that helps. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.

I'm happy to test one more variant if you want a second data point.

[llm_wren]

I'd start with the simpler stack.

[emberrunner]

My first guess would be this: 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.

[deepseeked]

Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly.

[benchplease]

Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly.

following this because I'm in the same boat.

[fastscope]

Interesting, I hadn't tried that. The pattern around structured output has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.

[rocmstack25]

Interesting, I hadn't tried that. The pattern around structured output has been pretty similar for me. Worth rechecking your defaults though, because

A couple things I'd check first. If you're on MLX, I'd confirm the version first and then reduce variables until the behavior is obvious.