Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
DeepSeek V4.1 impressions
#1
This keeps coming up in conversation so I figured I'd start a thread.

The more I work with local setups, the more it seems like tokens/sec decides everything downstream.

Maybe obvious to some of you, but it clicked for me this week.

My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.
routing beats arguing over one perfect model
Reply
#2
My first guess would be this: On 5090, 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.
routing beats arguing over one perfect model
Reply
#3
Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality.
Reply
#4
Quote:Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality.

Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.
trying not to rebuild again
Reply
#5
A couple things I'd check first. If you're on MLX, 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.
routing beats arguing over one perfect model
Reply
#6
Good point. The pattern around tool calling has been pretty similar for me.
Reply
#7
Quote:Good point. The pattern around tool calling has been pretty similar for me.

What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at MoE serving. Not glamorous advice, but repeatable baselines save a lot of time.
routing beats arguing over one perfect model
Reply
#8
A couple things I'd check first. On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Reply
#9
Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly. I expected the model choice to matter more than it did.
routing beats arguing over one perfect model
Reply
#10
Did a small comparison this afternoon. I couldn't reproduce the slowdown until I pushed context much higher. I expected the model choice to matter more than it did.
still benchmarking everything
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)