+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Training & Customization (https://www.datasculpting.ai/inference/forumdisplay.php?fid=13)
+--- Forum: Model Merging (https://www.datasculpting.ai/inference/forumdisplay.php?fid=57)
+--- Thread: do you even need a vector DB here for Mistral (/showthread.php?tid=1246)
Pages:
1
2
do you even need a vector DB here for Mistral - vectorhouse71 - 10-14-2026
Did a bit of testing and thought I'd post the result here.
Short version: PyTorch behaved well for me, but only after I stopped ignoring NVFP4.
Curious if anyone else landed in the same place.
My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.
Re: do you even need a vector DB here for Mistral - embersmith - 10-15-2026
that fixed it for me too.
Re: do you even need a vector DB here for Mistral - rocmplane - 10-18-2026
Quote:that fixed it for me too.
Good point. The pattern around MoE serving has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Re: do you even need a vector DB here for Mistral - kernelghost - 10-18-2026
Quote:Quote:that fixed it for me too.
That matches what I was seeing. The pattern around long context has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Re: do you even need a vector DB here for Mistral - kernelgrid - 10-18-2026
I'd approach it in a boring order. On M3 Max, 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: do you even need a vector DB here for Mistral - audiopath66 - 10-18-2026
I'd approach it in a boring order. On 5090, 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.
Re: do you even need a vector DB here for Mistral - labpath - 10-18-2026
My first guess would be this: If you're on SGLang, I'd confirm the version first and then reduce variables until the behavior is obvious.
Re: do you even need a vector DB here for Mistral - batchember - 10-18-2026
Quote:A couple things I'd check first. On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives.
I hit almost the same issue last night.
Re: do you even need a vector DB here for Mistral - tinycontext - 10-18-2026
I tested this tonight. On 5090 with MLX, I saw basically the same behavior. The main thing that moved was latency, not quality.
Re: do you even need a vector DB here for Mistral - modbench - 10-18-2026
I'd start with the simpler stack.