Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
recipes for a good local stack
#11
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal.
M3 Max • MLX • local-first
Reply
#12
Quote:Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal.

I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at long context. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply
#13
Thanks, that helps. I ended up in about the same place using llama.cpp.
Reply
#14
I tested this tonight. On M3 Max with llama.cpp, I saw basically the same behavior.
trying not to rebuild again
Reply
#15
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. At this point the real bottleneck is my patience.
M3 Max • MLX • local-first
Reply
#16
worth checking the driver first.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)