![]() |
|
Search / Retrieval / Reranking discussion - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: RAG & Knowledge Systems (https://www.datasculpting.ai/inference/forumdisplay.php?fid=14) +--- Forum: Search / Retrieval / Reranking (https://www.datasculpting.ai/inference/forumdisplay.php?fid=61) +--- Thread: Search / Retrieval / Reranking discussion (/showthread.php?tid=512) Pages:
1
2
|
Re: Search / Retrieval / Reranking discussion - quantshed - 09-30-2026 Quote:What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Kimi and compare from there. 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. Re: Search / Retrieval / Reranking discussion - tensorkite - 09-30-2026 Can you fill in a bit more context? Is this local-only or are you routing anything externally? Re: Search / Retrieval / Reranking discussion - prompttinker44 - 09-30-2026 worth checking the driver first. Re: Search / Retrieval / Reranking discussion - thetafield - 09-30-2026 My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Kimi and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it. Re: Search / Retrieval / Reranking discussion - rocmpath - 10-01-2026 I'd approach it in a boring order. On GB200, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glamorous advice, but repeatable baselines save a lot of time. |