Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
recipes for a good local stack
#1
Thought I'd post a small recipe because a lot of threads ask similar things.

This isn't revolutionary, but the combination of MLX and Threadripper box felt surprisingly usable once I tuned around quant drift.

Maybe useful as a starting point for newer folks.
Reply
#2
Quote:Thought I'd post a small recipe because a lot of threads ask similar things.

What exact setup are you running? Are you testing this on 4090 or something else?
M3 Max • MLX • local-first
Reply
#3
A couple questions before I guess too hard. What model, what runtime, and roughly what context size?
Reply
#4
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at consumer GPUs. Not glamorous advice, but repeatable baselines save a lot of time.
Reply
#5
Appreciate the detail. I don't think your conclusion is far off.
Reply
#6
Need a little more detail here. Are you testing this on Threadripper box or something else?
still benchmarking everything
Reply
#7
Quote:Need a little more detail here. Are you testing this on Threadripper box or something else?

following this because I'm in the same boat.
small models can still be good
Reply
#8
What worked for me was pretty simple. If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious.
learning in public
Reply
#9
What worked for me was pretty simple. On dual 3090, the easiest win is often to back off the aggressive settings and see whether the problem survives. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#10
same here on my side.
still benchmarking everything
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)