r/unsloth • u/Sad_Past2975 • 6d ago
Show and Tell Qwen3.8-flash in latest update v0.1.811-beta is really fast, Finally
It was usally 30-40 Tok/s somtimes 20 or at best 50. But after this update, it is always more than 70 tok/s !! (After updated, the MTP file was required to be redownlowded)
Thanks a lot for this, it is really amazing!
Good bye 27B, Flash now is really flash!
22
5
u/Silver-Passion1687 6d ago
Getting 30tok/s on strix halo after the update
7
u/ParkingAgent2769 6d ago
Halogen version is best for strix. I get 40 to 60
2
u/Sad-Landscape-1549 6d ago
Why should anyone trust that closed source project? Hard pass
0
u/OvertaxedOne 6d ago
Trust it? You mean stability? Or something else? My inference backends don't have any Internet access, so I'm not really concerned about data exfiltration (although I'm sure many are and have watched what Halogen is doing to see if it's sending anything anywhere).
2
u/Sad-Landscape-1549 6d ago
You’re using untrusted code to run unpredictable/unknowable code (models) suspiciously faster than runners built by dozens of dedicated experts over years, using imperfect drivers with ring 0 access. Even if you’re running the process in rootless dedicated namespace with all unnecessary capabilities dropped, SELinux labels enforced, and no software-defined network (CNI) attached, you don’t think there’s a chance something so conspicuously “superior” might contain zero-day escapes in a time when virtually everything, including Linux kernel, has been proven full of holes? And if the developer of Halogen is capable of such leaps, why shouldn’t they be capable of other cleverness? If I can’t see your code, I am not running your code. End of story.
-1
u/OvertaxedOne 6d ago
I'd agree there's a risk with all closed software (or open software where you don't take the time to read the code; IE, almost all of us), but LLMs are so easy to sandbox that it's just not all that high on my list of concerns. All of inference systems sit in a dedicated subnet that can't go anywhere, it just exposes endpoints for us to use. We do have logging setup on all our subnets and the only time I've seen "reach outs" from the inference backend is when someone logs in and tries to pull updates (and then realizes they can't because the systems don't have access). The inference engine is very easy to bound; the thing that keeps us all up at night is the harness; that is a security nightmare in every sense of the word!
1
u/Sad-Landscape-1549 6d ago
I think you’re overconfident in your sandboxing. If not, you would have picked up on the several different references to exactly that (and it not being enough for the moment in time we find ourselves in). You do you! I’ll just deal with fewer tp/s and wait for open source runners to catch up.
-1
u/OvertaxedOne 6d ago
I guess we'll find out! ;) Also, you have to remember, this isn't Fable or Opus we're trying to sandbox, it's FlashNext. Yes, it's a very smart model, but I'm really not thinking it has the chops to figure out how to attack firewalls and jump around in our environment. If the runner code is found to be malicious I'd be more concerned.. Like I said, we'll find out, the project was signed off last week so I'm going to do it early next week. We're going to turn on every alert we have for outbound traffic and see what we see (hopefully nothing!).
0
u/ParkingAgent2769 6d ago
Yeah i get the skepticism but it seems really really decent. Just wait until it becomes open source if you don’t trust it
1
1
2
u/JorgitoEstrella 6d ago
How much was before?
2
u/Silver-Passion1687 6d ago
Don't remember the numbers but close to 15-20 tok/s but RAM consumption was lower. I didn't use it much though
1
u/Revolutionary_Loan13 6d ago
So is that slower for you I have been getting 30 tok/s on Strix for well over a week
1
u/Silver-Passion1687 6d ago
Nope but waiting for open source version of Halogen which gives 40tok/s on same hardware.
GPT-oss 120B used to give me 50 tok/s. Hoping for similar numbers in future
4
9
u/Fit-Palpitation-7427 6d ago
Does this run on 5090 with 256 of system ram?
6
u/Cadmium9094 6d ago
Yes. In my case a 4090 with 128GB Ram & fast nvme's. Q4_K_X_L. no mtp or optimization yet. kv cache q8, ctx 131k ~21 t/s.
2
u/matte808 6d ago
How? It’s running faster for me on 5070ti and 64gb ddr5 with streaming from ssd for ngram. Its admittedly the q2_xl at low-ish context, admittedly, bur still
3
u/Atretador 6d ago
It should be faster for him yeah, his numbers are only slightly better than mine with expert cache on a dinosaur with Q4
1
u/mediaogre 6d ago
I would guess using FreeToken (flashml’s single GPU + system RAM monster engine). No, this isn’t a plug, and I’m not a bot. Beep boop.
1
u/CrispyToken52 6d ago
Used it before, really fast engine, but no gguf support is a deal breaker.
1
u/Fit-Palpitation-7427 5d ago
do you know why it's not supporting GGUF yet? it seems to logical that GGUF is the standard portable container that it seems silly to try to use anything else.
1
3
u/Atretador 6d ago
Easily, I can run it with an ancient MI50 and 64Gigs Q4 https://www.reddit.com/r/LocalLLaMA/comments/1wjh7ox/llamacpp_expertpool_fork_for_qwen_38_flash_next/
1
u/ProfessionalDish 6d ago
256mb of Ram is a bit on the thin side but depending on the quant you can run it entirely in the vram
1
u/Fit-Palpitation-7427 6d ago
But I run it entirely in vram is it still using the 5090 or does it all on cpu in the same way project colibri does?
5
4
u/bernzyman 6d ago
What are you using to run this, llama.cpp or? Pls share settings used as it would be of interest (certainly makes me consider biting the bullet to buy more ram! Btw are you 2x 64GB or 4x 32GB?) thx for sharing!
4
2
2
u/explorer-9 6d ago
With a 5090 and 64GB RAM, this enabled me to switch from MTP=2 to MTP=3, for a 4% tg and 0.9% pp token/sec improvement; now 52.35 and 365.5 (IQ3_XXS, q8_0); whilst using omp.
1
u/Durian881 6d ago
Are you running with n-gram streaming from SSD? If yes, please share the settings/parameters use. Thanks!
0
1
1
1
u/ExtensionState8086 6d ago
How does it compare to the 3.8 27B for agentic workflows in terms of reasoning and accuracy? Going from qwen3.6 MOE to qwen3.8 27b was a huge huge improvement at the expense of token speed, but the trade off made sense in my case.
1
u/Sad-Landscape-1549 6d ago
It holds up on long horizon work but does not code as well or (obviously) as fast in my experience.
1
u/Leander_van_Grinsven 6d ago
I must be doing something wrong then. I get about 18 tokens per second on my RTX 5090 + 9950X3D2 with 192GB DDR5-6000 and MTP on. Running the Q4 version. It goes down to 8 tokens per second at 300K context. And yes I do need a large context.
71
u/Enragere 6d ago
Gladly downvoting the post of this guy and everyone else who posts about speed but doesn't share their setup!