![]() |
|
vector DB that stayed out of the way: anyone testing this? - Printable Version +- 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: vector DB that stayed out of the way: anyone testing this? (/showthread.php?tid=476) Pages:
1
2
|
Re: vector DB that stayed out of the way: anyone testing this? - quietarch - 10-06-2026 Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly. Re: vector DB that stayed out of the way: anyone testing this? - relayforge - 10-06-2026 Not sure I agree there. I get why that seems right, but on 7900 XTX the bottleneck felt elsewhere. Re: vector DB that stayed out of the way: anyone testing this? - cacheplane98 - 10-06-2026 My first guess would be this: On M3 Max, the easiest win is often to back off the aggressive settings and see whether the problem survives. Re: vector DB that stayed out of the way: anyone testing this? - benchplease - 10-07-2026 A couple things I'd check first. If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious. |