Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
long context that stayed useful
#1
Posting this in case it saves someone else a little time.

I'm not trying to build a perfect architecture diagram. I just want a sane starting point around LM Studio and mini PC.

Would rather learn from your scars than collect my own all at once.
Reply
#2
same here on my side.
Reply
#3
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.
Reply
#4
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Llama and compare from there.
curious and caffeinated
Reply
#5
That matches what I was seeing. 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
#6
Thanks, that helps. The pattern around router policy has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Apple Silicon • MLX mostly
Reply
#7
That matches what I was seeing. That matches what I saw on B200. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply
#8
Quote:That matches what I was seeing. That matches what I saw on B200. I got better results once I stopped chasing one metric and just looked at whether the

same here on my side.
Reply
#9
following this because I'm in the same boat.
still benchmarking everything
Reply
#10
worth checking the driver first.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)