Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
release notes that matter
#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 reranking decides everything downstream.

Curious whether that lines up with what other people are seeing.

For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
routing beats arguing over one perfect model
Reply
#2
Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit.
retrieval before vibes
Reply
#3
What worked for me was pretty simple. If you're on TensorRT-LLM, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.
routing beats arguing over one perfect model
Reply
#4
Can you fill in a bit more context? What model, what runtime, and roughly what context size?
Reply
#5
Good point. That matches what I saw on dual 3090. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
routing beats arguing over one perfect model
Reply
#6
Quote:Good point. That matches what I saw on dual 3090. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread lo

Good point. That matches what I saw on B200. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
routing beats arguing over one perfect model
Reply
#7
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at prefix caching.
Reply
#8
Tried to reproduce it just now. On GB200 with MLX, I saw basically the same behavior. The main thing that moved was latency, not quality.
routing beats arguing over one perfect model
Reply
#9
My first guess would be this: On M3 Max, 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.
Reply
#10
A couple things I'd check first. On 7900 XTX, the easiest win is often to back off the aggressive settings and see whether the problem survives. Once you know the plain path works, then add the faster path back in piece by piece.
routing beats arguing over one perfect model
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)