Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Vector Databases discussion on A6000
#1
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.
trying not to rebuild again
Reply
#2
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.
Reply
#3
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.
context windows are not a product strategy
Reply
#4
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.
Reply
#5
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.
context windows are not a product strategy
Reply
#6
Thanks, that helps. The pattern around consumer GPUs has been pretty similar for me.
small models can still be good
Reply
#7
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.
Reply
#8
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.
context windows are not a product strategy
Reply
#9
worth checking the driver first.
mostly local
Reply
#10
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.
context windows are not a product strategy
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)