Inference
Vector Databases discussion on A6000 - Printable Version

+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: RAG & Knowledge Systems (https://www.datasculpting.ai/inference/forumdisplay.php?fid=14)
+--- Forum: Vector Databases (https://www.datasculpting.ai/inference/forumdisplay.php?fid=60)
+--- Thread: Vector Databases discussion on A6000 (/showthread.php?tid=131)



Vector Databases discussion on A6000 - relayforge - 09-05-2026

Thought I'd post a small recipe because a lot of threads ask similar things.

Just sharing a setup that ended up working reasonably well: Phi, MLX, A6000, with a lot of attention on reranking.

If someone wants the exact settings I can clean them up and post them.


Re: Vector Databases discussion on A6000 - orbitbench6 - 09-05-2026

Quote:Thought I'd post a small recipe because a lot of threads ask similar things.

What worked for me was pretty simple. On 7900 XTX, 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: Vector Databases discussion on A6000 - tinycontext - 09-08-2026

Quote:
Quote:Thought I'd post a small recipe because a lot of threads ask similar things.

I don't think that's the whole story. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.

If you post your exact settings, people here can probably narrow it down pretty fast.


Re: Vector Databases discussion on A6000 - emberquill - 09-08-2026

Maybe, but I had the opposite result. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model.


Re: Vector Databases discussion on A6000 - tinycontext - 09-08-2026

Did a small comparison this afternoon. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality.

If you post your exact settings, people here can probably narrow it down pretty fast.


Re: Vector Databases discussion on A6000 - batchember - 09-08-2026

Thanks, that helps. The pattern around consumer GPUs has been pretty similar for me.


Re: Vector Databases discussion on A6000 - minthall - 09-08-2026

My first guess would be this: On dual 3090, the easiest win is often to back off the aggressive settings and see whether the problem survives.


Re: Vector Databases discussion on A6000 - tinycontext - 09-08-2026

Thanks, that helps. The pattern around consumer GPUs has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. The logs were somehow calmer than I was.


Re: Vector Databases discussion on A6000 - batchscope72 - 09-10-2026

worth checking the driver first.


Re: Vector Databases discussion on A6000 - tinycontext - 09-11-2026

Interesting, I hadn't tried that. I ended up in about the same place using MLX. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.