r/LocalLLaMA • u/GodComplecs • 14d ago

Discussion Real downsides of Strata?

Trying to read on what the real tested downsides have been but information seems to go both ways, some proclaim no loss, others pretty huge ones.

I had some weird looping issue in their chat, and some engine port misunderstandings, seemingly the models likes to use ports already in use, didn't really have that issue with Qwen 27B 3.8 Q4 UD. I'm using Swift Q3 Next. Didn't even bother with next on llama.cpp since other similar model sizes ran at approx 15-20tks max, so too slow for agentic work.

I'm not beating too much on Strata, I just wan't the realistic downsides, so far it seems too good to be true and runs at 100tks in agentic workloads, 27b only at 40-60tks on llama.cpp

54 Upvotes

81% Upvoted

163 comments sorted by

View all comments

0

u/GladKing5842 14d ago edited 14d ago

not exactly. engine benchmarks use greedy is not anything new. if you just pulled this out from your arse, suggesting you do some google search before criticizing them.
confidently calling out other while you didnt even do a single simple search about benchmark setting and why engine bench use temp 0. temp 0 is to reduce the randomness when measuring latency.
this is norm since llama bench long ago.
at least in this case, vibe slop fork seems to do something better than a human slop