Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
hybrid retrieval results for Mistral
#1
Maybe I'm missing something obvious.

I'm trying to decide whether to keep the current stack or change course. Main question is how people here are handling quant drift.

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

I care more about stability than squeezing the last possible tokens/sec out of it.
Reply
#2
Quote:Maybe I'm missing something obvious.

A couple things I'd check first. On M3 Max, 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.
Reply
#3
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there.
curious and caffeinated
Reply
#4
Quote:I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there.

Interesting, I hadn't tried that. That matches what I saw on mini PC. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. I keep promising myself this is the last rebuild.
rack in the garage • local models everywhere
Reply
#5
Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit.
Reply
#6
Interesting, I hadn't tried that. That matches what I saw on A6000. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
rack in the garage • local models everywhere
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)