Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
4090 vs 5090 for 70B quants
#1
Spent some time on this today and wanted to compare notes.

I've gone back and forth between PyTorch and MLX for Kimi. The interesting difference for me has been HBM constraints.

Trying to avoid rebuilding the whole thing twice.
Reply
#2
Quote:Spent some time on this today and wanted to compare notes.

Appreciate the detail. 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
#3
subscribed, curious where this lands.
7900 XTX / ROCm / somehow still optimistic
Reply
#4
That matches what I was seeing. I ended up in about the same place using vLLM. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply
#5
Quote:That matches what I was seeing. I ended up in about the same place using vLLM. I got better results once I stopped chasing one metric and just looked

I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher.
retrieval before vibes
Reply
#6
A couple things I'd check first. 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
#7
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.
retrieval before vibes
Reply
#8
following this because I'm in the same boat.
small models can still be good
Reply
#9
A couple questions before I guess too hard. Is this local-only or are you routing anything externally?
7900 XTX / ROCm / somehow still optimistic
Reply
#10
Good point. I ended up in about the same place using SGLang.
learning in public
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)