+- 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: setup advice (/showthread.php?tid=1034)
Pages:
1
2
do you even need a vector DB here: setup advice - deltagrid - 10-10-2026
This keeps coming up in conversation so I figured I'd start a thread.
One thing I keep noticing is that people underestimate continuous batching until they actually try to run this stuff for more than one afternoon.
Wondering if this is just where the whole space is heading now.
This is mostly for local work rather than public serving.
Re: do you even need a vector DB here: setup advice - sparrowghost - 10-12-2026
Can you fill in a bit more context? Are you testing this on B200 or something else?
Re: do you even need a vector DB here: setup advice - modgarden - 10-12-2026
Tried to reproduce it just now. My result was mixed: first run looked bad, second run looked normal. The main thing that moved was latency, not quality.
Re: do you even need a vector DB here: setup advice - oxiderunner - 10-12-2026
that fixed it for me too.
Re: do you even need a vector DB here: setup advice - routearch - 10-13-2026
Quote:that fixed it for me too.
worth checking the driver first.
Re: do you even need a vector DB here: setup advice - cacheline - 10-13-2026
That matches what I was seeing. I ended up in about the same place using llama.cpp. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Re: do you even need a vector DB here: setup advice - tensorfield88 - 10-13-2026
Good point. I ended up in about the same place using SGLang.
Re: do you even need a vector DB here: setup advice - macrotinker - 10-13-2026
Not sure I agree there. I've seen people blame batch size when the real issue was much more mundane. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Re: do you even need a vector DB here: setup advice - embersmith - 10-14-2026
A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at consumer GPUs. 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: setup advice - promptfield - 10-14-2026
I hit almost the same issue last night.