Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
QLoRA resource reality check with LM Studio
#1
Has anyone else run into this?

My current setup is LM Studio with GB200, and I keep running into token cost.

If you've tested something similar, what did you keep and what did you stop bothering with?

My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.
still benchmarking everything
Reply
#2
What worked for me was pretty simple. On Threadripper box, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
learning in public
Reply
#3
Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher.
Reply
#4
That matches what I was seeing. I don't think your conclusion is far off. The biggest change for me was simplifying the stack instead of adding one more optimization layer. I keep promising myself this is the last rebuild.
measure twice, benchmark three times
Reply
#5
Maybe, but I had the opposite result. I get why that seems right, but on 7900 XTX the bottleneck felt elsewhere. Worth testing the simpler explanation before adopting the more interesting one.
learning in public
Reply
#6
Need a little more detail here. Is this local-only or are you routing anything externally?
Reply
#7
Quote:Need a little more detail here. Is this local-only or are you routing anything externally?

Thanks, that helps. I ended up in about the same place using PyTorch. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#8
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at tool calling.
Reply
#9
Thanks, that helps. The pattern around continuous batching 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.
learning in public
Reply
#10
Quote:Thanks, that helps. The pattern around continuous batching has been pretty similar for me. I got better results once I stopped chasing one metric and

I'd start with the simpler stack.
post logs or it didn't happen
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)