09-21-2026, 06:48 AM
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal.
M3 Max • MLX • local-first
|
recipes for a good local stack
|
|
09-21-2026, 06:48 AM
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal.
M3 Max • MLX • local-first
09-21-2026, 03:39 PM
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.
09-21-2026, 05:46 PM
Thanks, that helps. I ended up in about the same place using llama.cpp.
09-21-2026, 10:13 PM
I tested this tonight. On M3 Max with llama.cpp, I saw basically the same behavior.
trying not to rebuild again
09-22-2026, 06:53 AM
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
09-22-2026, 07:05 PM
worth checking the driver first.
|
|
« Next Oldest | Next Newest »
|