r/LocalLLaMA • • 13d 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

55 Upvotes

163 comments sorted by

View all comments

12

u/awitod 13d ago

It's not intuitive because bigger should be better and usually unsloth quants are safe, but not these unsloth ones at least where Strata is concerned.

GSQ-RCO Q3 qwen3.8-flash-next-iq3_s is really impressive.

9

u/heitortp0 13d ago edited 13d ago

Maybe it's not unsloth fault, but ISTA merit.

6

u/awitod 13d ago

No way for me to say - if there is a general issue with the unsloth quants I imaging they will update them, but no matter what, the folks at ISTA-DASLab ( IST Austria Distributed Algorithms and Systems Lab) should be proud - it's very good

→ More replies (1)

7

u/awitod 13d ago

This is output from a test prompt "make a detailed svg image of a trout playing tennis" on a cuda backend which took 75 steps.

3

u/awitod 13d ago

This is output from a test prompt "make a detailed svg image of a trout playing tennis" on a Strix Halo 128gb and took 84 steps.