Posts: 40
Threads: 8
Joined: Sep 2026
Reputation:
0
Spent some time on this today and wanted to compare notes.
I've gone back and forth between Ollama and MLX for DeepSeek. The interesting difference for me has been long context.
Interested in tradeoffs more than fan loyalty.
Posts: 52
Threads: 5
Joined: Aug 2026
Reputation:
0
Appreciate the detail. That matches what I saw on A6000. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
trying not to rebuild again
Posts: 62
Threads: 6
Joined: Sep 2026
Reputation:
0
A couple things I'd check first. If you're on TensorRT-LLM, I'd confirm the version first and then reduce variables until the behavior is obvious.
Posts: 52
Threads: 6
Joined: Sep 2026
Reputation:
0
I'd start with the simpler stack.
Posts: 341
Threads: 51
Joined: Sep 2026
Reputation:
0
Quote:I'd start with the simpler stack.
Interesting, I hadn't tried that. I ended up in about the same place using llama.cpp. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
measure twice, benchmark three times
Posts: 35
Threads: 5
Joined: Sep 2026
Reputation:
0
Thanks, that helps. The pattern around reranking has been pretty similar for me. Turns out 'just one more test' was a lie.
Posts: 62
Threads: 4
Joined: Sep 2026
Reputation:
0
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at INT4. Once you know the plain path works, then add the faster path back in piece by piece.
Posts: 37
Threads: 2
Joined: Aug 2026
Reputation:
0
My first guess would be this: Before rebuilding anything, I'd test one clean baseline with FLUX and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.
small models can still be good