Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
search and retrieval tuning tips
#1
This keeps coming up in conversation so I figured I'd start a thread.

The more I work with local setups, the more it seems like prefix caching decides everything downstream.

Curious whether that lines up with what other people are seeing.
rack in the garage • local models everywhere
Reply
#2
I'd approach it in a boring order. On GB200, the easiest win is often to back off the aggressive settings and see whether the problem survives.
retrieval before vibes
Reply
#3
Appreciate the detail. I ended up in about the same place using SGLang.
Reply
#4
Quote:Appreciate the detail. I ended up in about the same place using SGLang.

Need a little more detail here. Is this local-only or are you routing anything externally?
curious and caffeinated
Reply
#5
Good point. That matches what I saw on A6000.
retrieval before vibes
Reply
#6
Did a small comparison this afternoon. My result was mixed: first run looked bad, second run looked normal. I expected the model choice to matter more than it did.
curious and caffeinated
Reply
#7
A couple things I'd check first. If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious.
Reply
#8
I'd start with the simpler stack.
retrieval before vibes
Reply
#9
Interesting, I hadn't tried that. That matches what I saw on 5090. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
rack in the garage • local models everywhere
Reply
#10
Good point. The pattern around tail latency has been pretty similar for me.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)