Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
which hosted model is actually worth paying for 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 speculative decoding.

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.
routing beats arguing over one perfect model
Reply
#2
Interesting, I hadn't tried that. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
routing beats arguing over one perfect model
Reply
#3
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher.
Reply
#4
Quote:I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher.

What worked for me was pretty simple. On 5090, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
routing beats arguing over one perfect model
Reply
#5
I'd start with the simpler stack.
Reply
#6
that fixed it for me too.
routing beats arguing over one perfect model
Reply
#7
My first guess would be this: If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time.
Reply
#8
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. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
routing beats arguing over one perfect model
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)