+- 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 (/showthread.php?tid=366)
do you even need a vector DB here - dockember - 09-20-2026
This keeps coming up in conversation so I figured I'd start a thread.
It feels like the conversation has shifted hard toward inference and serving details lately, and honestly that makes sense once you start dealing with long context.
Maybe obvious to some of you, but it clicked for me this week.
Re: do you even need a vector DB here - quiettoken - 09-21-2026
A couple things I'd check first. 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: do you even need a vector DB here - cobaltlab - 09-21-2026
Need a little more detail here. What model, what runtime, and roughly what context size?
Re: do you even need a vector DB here - llm_wren - 09-21-2026
worth checking the driver first.
Re: do you even need a vector DB here - ggufwire22 - 09-21-2026
I think the bottleneck is somewhere else. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Re: do you even need a vector DB here - edgecoast - 09-21-2026
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.