Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Multimodal discussion
#11
I think the bottleneck is somewhere else. I've seen people blame quant drift when the real issue was much more mundane. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Reply
#12
Did a small comparison this afternoon. On A6000 with MLX, I saw basically the same behavior.
retrieval before vibes
Reply
#13
Quote:Did a small comparison this afternoon. On A6000 with MLX, I saw basically the same behavior.

What exact setup are you running? Do you see the same thing with a smaller batch or shorter prompt?
Reply
#14
same here on my side.
small models can still be good
Reply
#15
I'd approach it in a boring order. If you're on llama.cpp, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.
image models by night, local pipelines by day
Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)