Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
simple local serving recipe: anyone testing this?
#1
Posting this in case it saves someone else a little time.

I'm helping a small team set up a local workflow. We don't need a giant stack, but we do care about tail latency.

I'm especially interested in mistakes worth avoiding.

For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
Reply
#2
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.
M3 Max • MLX • local-first
Reply
#3
A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
still benchmarking everything
Reply
#4
A couple things I'd check first. If you're on SGLang, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.
still benchmarking everything
Reply
#5
Quote:A couple things I'd check first. If you're on SGLang, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you

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.
learning in public
Reply
#6
same here on my side.
Reply
#7
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at batch size. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
7900 XTX / ROCm / somehow still optimistic
Reply
#8
Quote:My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at batch size. A lot of these th

A couple things I'd check first. On mini PC, 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.
curious and caffeinated
Reply
#9
Interesting, I hadn't tried that. The pattern around prefix caching has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#10
Appreciate the detail. I don't think your conclusion is far off.
learning in public
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)