Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Apple unified memory limits
#1
Maybe I'm missing something obvious.

I'm trying to decide whether to keep the current stack or change course. Main question is how people here are handling reranking.

Not looking for the perfect answer, mostly what worked in real use.
trying not to rebuild again
Reply
#2
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at KV cache pressure. Not glamorous advice, but repeatable baselines save a lot of time.

I'm happy to test one more variant if you want a second data point.
throughput matters, but tail latency matters too
Reply
#3
A couple things I'd check first. On A6000, the easiest win is often to back off the aggressive settings and see whether the problem survives.
learning in public
Reply
#4
following this because I'm in the same boat. I keep promising myself this is the last rebuild.
M3 Max • MLX • local-first
Reply
#5
Maybe, but I had the opposite result. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Worth testing the simpler explanation before adopting the more interesting one.
Reply
#6
What exact setup are you running? Is this local-only or are you routing anything externally?
throughput matters, but tail latency matters too
Reply
#7
Tried to reproduce it just now. I couldn't reproduce the slowdown until I pushed context much higher.
trying not to rebuild again
Reply
#8
worth checking the driver first.
Reply
#9
I hit almost the same issue last night.
Reply
#10
subscribed, curious where this lands.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)