Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
best local open-weight model this week
#1
This keeps coming up in conversation so I figured I'd start a thread.

One thing I keep noticing is that people underestimate embeddings until they actually try to run this stuff for more than one afternoon.

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

If I had to summarize the lesson so far, it would be that clean setup and observability beat clever guesses.
Reply
#2
worth checking the driver first.
Reply
#3
What exact setup are you running? Is this local-only or are you routing anything externally?
trying not to rebuild again
Reply
#4
Quote:What exact setup are you running? Is this local-only or are you routing anything externally?

I'd approach it in a boring order. On dual 3090, 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
#5
Did a small comparison this afternoon. My result was mixed: first run looked bad, second run looked normal.
small models can still be good
Reply
#6
What worked for me was pretty simple. If you're on SGLang, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply
#7
Quote:What worked for me was pretty simple. If you're on SGLang, I'd confirm the version first and then reduce variables until the behavior is obvious. A lo

Not sure I agree there. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Worth testing the simpler explanation before adopting the more interesting one.

If you post your exact settings, people here can probably narrow it down pretty fast.
Reply
#8
Good point. The pattern around embeddings has been pretty similar for me.
Reply
#9
Quote:Good point. The pattern around embeddings has been pretty similar for me.

worth checking the driver first.
2x3090 • llama.cpp • too much VRAM is still not enough
Reply
#10
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)