Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
tools worth paying for with MLX
#1
Thought I'd post a small recipe because a lot of threads ask similar things.

Just sharing a setup that ended up working reasonably well: DeepSeek, SGLang, 5090, with a lot of attention on structured output.

Maybe useful as a starting point for newer folks. At this point the real bottleneck is my patience.
learning in public
Reply
#2
That matches what I was seeing. The pattern around tokens/sec has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
curious and caffeinated
Reply
#3
Quote:That matches what I was seeing. The pattern around tokens/sec has been pretty similar for me. The biggest change for me was simplifying the stack inst

Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed.
trying not to rebuild again
Reply
#4
I don't think that's the whole story. I've seen people blame KV cache pressure when the real issue was much more mundane.
mostly local
Reply
#5
Quote:I don't think that's the whole story. I've seen people blame KV cache pressure when the real issue was much more mundane.

I hit almost the same issue last night.
context windows are not a product strategy
Reply
#6
Good point. 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.
Reply
#7
following this because I'm in the same boat.
mostly local
Reply
#8
worth checking the driver first.
Reply
#9
Quote:worth checking the driver first.

Need a little more detail here. Is this local-only or are you routing anything externally?
watching release notes so you don't have to
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)