Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
where reranking mattered on mini PC
#1
Posting this in case it saves someone else a little time.

I'm helping a small team set up a local workflow. We don't need a giant stack, but we do care about INT4.

Would rather learn from your scars than collect my own all at once.
curious and caffeinated
Reply
#2
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.
Reply
#3
Quote:That matches what I was seeing. That matches what I saw on Threadripper box. I got better results once I stopped chasing one metric and just looked at

Thanks, that helps. The pattern around batch size has been pretty similar for me.
learning in public
Reply
#4
I hit almost the same issue last night.
Reply
#5
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.
Reply
#6
Need a little more detail here. Is this local-only or are you routing anything externally?
Reply
#7
I think the bottleneck is somewhere else. I get why that seems right, but on Threadripper box the bottleneck felt elsewhere. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
Reply
#8
Quote: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.

My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at speculative decoding. Not glamorous advice, but repeatable baselines save a lot of time.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Reply
#9
Did a small comparison this afternoon. On A6000 with SGLang, I saw basically the same behavior.
Reply
#10
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. Turns out 'just one more test' was a lie.
M3 Max • MLX • local-first
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)