Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
simple local serving recipe: setup advice
#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 A6000 felt surprisingly usable once I tuned around quant drift.

Maybe useful as a starting point for newer folks.
M3 Max • MLX • local-first
Reply
#2
Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?
measure twice, benchmark three times
Reply
#3
Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly.
Reply
#4
My first guess would be this: If you're on PyTorch, I'd confirm the version first and then reduce variables until the behavior is obvious.
Reply
#5
Can you fill in a bit more context? Is this local-only or are you routing anything externally?
Reply
#6
that fixed it for me too.
7900 XTX / ROCm / somehow still optimistic
Reply
#7
What exact setup are you running? Do you see the same thing with a smaller batch or shorter prompt?
Reply
#8
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at embeddings. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
learning in public
Reply
#9
I think the bottleneck is somewhere else. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Could be a workload difference, but I wouldn't generalize too fast from one setup.
7900 XTX / ROCm / somehow still optimistic
Reply
#10
Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?
still benchmarking everything
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)