Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
when video is still not worth the wait for DeepSeek
#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 MoE serving.

Would rather learn from your scars than collect my own all at once.
Reply
#2
Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?
Reply
#3
Maybe, but I had the opposite result. I've seen people blame speculative decoding when the real issue was much more mundane.
Reply
#4
I'd start with the simpler stack.
small models can still be useful
Reply
#5
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed.
Reply
#6
Need a little more detail here. Do you see the same thing with a smaller batch or shorter prompt?

If you post your exact settings, people here can probably narrow it down pretty fast.
Reply
#7
What worked for me was pretty simple. On M3 Max, the easiest win is often to back off the aggressive settings and see whether the problem survives.
mostly local
Reply
#8
Appreciate the detail. I ended up in about the same place using vLLM.
Reply
#9
Quote:Appreciate the detail. I ended up in about the same place using vLLM.

I hit almost the same issue last night.
Reply
#10
I'd start with the simpler stack.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)