Posts: 31
Threads: 6
Joined: Sep 2026
Reputation:
0
Did a bit of testing and thought I'd post the result here.
Short version: LM Studio behaved well for me, but only after I stopped ignoring workstation thermals.
Happy to post more details if anyone wants them.
trying not to rebuild again
Posts: 168
Threads: 14
Joined: Sep 2026
Reputation:
0
That matches what I was seeing. That matches what I saw on GB200. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
2x3090 • llama.cpp • too much VRAM is still not enough
Posts: 39
Threads: 5
Joined: Sep 2026
Reputation:
0
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at continuous batching. Not glamorous advice, but repeatable baselines save a lot of time.
Posts: 23
Threads: 3
Joined: Sep 2026
Reputation:
0
My first guess would be this: On GB200, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glamorous advice, but repeatable baselines save a lot of time.
Posts: 123
Threads: 18
Joined: Sep 2026
Reputation:
0
Quote:Appreciate the detail. The pattern around prefill/decode split has been pretty similar for me. I got better results once I stopped chasing one metric
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Qwen and compare from there.
post logs or it didn't happen
Posts: 168
Threads: 14
Joined: Sep 2026
Reputation:
0
worth checking the driver first.
2x3090 • llama.cpp • too much VRAM is still not enough
Posts: 35
Threads: 3
Joined: Sep 2026
Reputation:
0
Appreciate the detail. The pattern around prefill/decode split has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.