Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Threadripper build for inference
#1
Did a bit of testing and thought I'd post the result here.

I tried this with Qwen using LM Studio on B200. The headline result was better than I expected, but speculative decoding still ended up being the limiting factor.

Curious if anyone else landed in the same place.

This is mostly for local work rather than public serving.
image models by night, local pipelines by day
Reply
#2
Ran a quick check on my box. On dual 3090 with PyTorch, I saw basically the same behavior.
Reply
#3
I tested this tonight. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed.
2x3090 • llama.cpp • too much VRAM is still not enough
Reply
#4
That matches what I was seeing. I ended up in about the same place using SGLang. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply
#5
subscribed, curious where this lands.
rack in the garage • local models everywhere
Reply
#6
subscribed, curious where this lands.
Reply
#7
Thanks, that helps. That matches what I saw on 7900 XTX.
Reply
#8
Quote:Thanks, that helps. That matches what I saw on 7900 XTX.

That matches what I was seeing. I ended up in about the same place using Ollama. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#9
I'd start with the simpler stack.
Reply
#10
Did a small comparison this afternoon. My result was mixed: first run looked bad, second run looked normal. The main thing that moved was latency, not quality.
learning in public
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)