Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Vector Databases discussion with Ollama
#11
Good point. That matches what I saw on 7900 XTX. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
still benchmarking everything
Reply
#12
same here on my side.
Reply
#13
A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at embeddings. Once you know the plain path works, then add the faster path back in piece by piece.

I'm happy to test one more variant if you want a second data point. At this point the real bottleneck is my patience.
context windows are not a product strategy
Reply
#14
What worked for me was pretty simple. On A6000, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glamorous advice, but repeatable baselines save a lot of time.

If you post your exact settings, people here can probably narrow it down pretty fast.
Reply
#15
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal. The main thing that moved was latency, not quality.
Reply
#16
Can you fill in a bit more context? Are you testing this on 7900 XTX or something else?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)