Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Instinct pricing thoughts
#11
Good point. That matches what I saw on dual 3090. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply
#12
Thanks, that helps. The pattern around embeddings 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.
7900 XTX / ROCm / somehow still optimistic
Reply
#13
Quote:Thanks, that helps. The pattern around embeddings has been pretty similar for me. I got better results once I stopped chasing one metric and just look

I don't think that's the whole story. I get why that seems right, but on M3 Max the bottleneck felt elsewhere.
Reply
#14
My first guess would be this: If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious.
team red, team patient
Reply
#15
Not sure I agree there. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)