+- 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
Search / Retrieval / Reranking discussion - rasterbench - 09-26-2026
Spent some time on this today and wanted to compare notes.
I've gone back and forth between PyTorch and TensorRT-LLM for Mixtral. The interesting difference for me has been structured output.
Interested in tradeoffs more than fan loyalty.
Re: Search / Retrieval / Reranking discussion - localtinker - 09-27-2026
Appreciate the detail. 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.
Re: Search / Retrieval / Reranking discussion - batchwire - 09-27-2026
What worked for me was pretty simple. On 5090, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Re: Search / Retrieval / Reranking discussion - phasespark - 09-27-2026
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. Once you know the plain path works, then add the faster path back in piece by piece.
Re: Search / Retrieval / Reranking discussion - batchsize - 09-27-2026
Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. I expected the model choice to matter more than it did.
Re: Search / Retrieval / Reranking discussion - vrampilot - 09-27-2026
My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.
Re: Search / Retrieval / Reranking discussion - routeline23 - 09-28-2026
I'd approach it in a boring order. If you're on llama.cpp, 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.
Re: Search / Retrieval / Reranking discussion - dockriver - 09-29-2026
Quote:I'd approach it in a boring order. If you're on llama.cpp, I'd confirm the version first and then reduce variables until the behavior is obvious. Once
that fixed it for me too.
Re: Search / Retrieval / Reranking discussion - cacheline - 09-29-2026
I tested this tonight. On 5090 with LM Studio, I saw basically the same behavior. The surprise was that memory pressure showed up before throughput collapsed.
Re: Search / Retrieval / Reranking discussion - benchplease - 09-30-2026
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Kimi and compare from there.