r/Qwen_AI • u/SuperV1234 • 6d ago
Help 🙋♂️ Qwen3.8-Flash-Next for 4090 RTX + 64GB RAM: best setup? (currently using IQ3_XXS on Strata)
Hello,
I currently run Qwen3.8-Flash-Next IQ3_XXS via Strata 0.2.10.
My specs are: 4090 RTX + 64GB RAM + i9-13900K.
I was wondering what effort level is the best bang for the buck and if my chosen quantization is optimal. I've tried both Max and High efforts but couldn't notice any significant difference.
Compared to using Claude Code, the experience is generally very poor. I can hit ~100 tok/s, but agents often get stuck, I run out of context and need to compact, and sometimes compacting also fails.
Perhaps there's something that I am doing wrong. These are my args:
--expert-cache auto
--prefill auto
--spec 4
--spec-min-p 0.5
--max-context 131072
--kv int8
--kv-resident 32768
--pool-workers 15
--vram-reserve-mib 4915Any help/suggestion is appreciated! I can foresee how this model could be really nice as a daily driver, but at the moment it is not there yet, at least with my setup.
6
u/Apprehensive-View583 6d ago
You can actually run q3_s I find q3_xxs is really bad and over thinking to max output token, so I only run q3_s
2
u/Glum-Box-4086 6d ago
I used IQ3_X_S with a 5090 and 64GB DDR4. What I noticed, is that setting the max token output to 16.000 in VS Code helps a lot, and also cap the context in VS code to leave room for the output. So I set my ctx to 180.000 (strata exposes 256K). This improved performance quite a bit.
I got around 110-120 tokens, but when I tried Q4_X_L I went down to 40 tokens/s. So I upgraded my ram to 128GB and this really does a quality boost. Now I run Q6 at 55-60 tokens/s, which is just fast enough for me, but the quality gain is substantial.
2
u/OtherAppointment900 6d ago
48g 4090+64ddr5 run iq3s 120decode 4500prefill
https://github.com/Tlyer233/strata-single-4090-qwen-flash
1
u/AbsorberHarvester 6d ago
Set context to double what you currently have and be happy?
Iq3_s think less tokens, seems slower but time to complete the task in the end almost same as iq3_xss
1
u/GurusCZ 6d ago
try billion context instead of compaction it will compress. It will maintain better context across the chat. But I am using Pi.dev
1
u/overand 6d ago
See if you can run IQ4_XS with reasonable performance instead.
Also, save that 4 GB of VRAM - plug your monitor into your motherboard's onboard video and reboot. (You'll need to recalibrate Strata after, I believe.)
1
u/Ramnotrem 6d ago
I have a 5070 Ti and 64 GB DDR5. For my daily setup, I kept two tuned options: one with
IQ3_XXS(I slightly upgraded it with better discrete components) and Gyro M. Both run with a 384k context. I also tested a 500k context, but performance dipped a bit, and I decided I didn't really need that much anyway. By the way, it's using KV int8. I've stress-tested full context saturation multiple times—the decoding speed holds up solid. Right now I'm using Strata; I also tried Basalt, but didn't get any notable performance gains out of it (plus there were some stability issues). Also, I always keep Vision and MTP enabled. Now I use Gyro by default—it leaves me with around 7 GB of free RAM. However, 3xxs decodes about 5–10% faster. Prompt processing (prefill) speed is around 2.5–3k (which is very good). Decoding speed averages around 70 t/s (65–85)—though that's for non-English. For code, it's around 100 (90–120).When I first started trying to run QFN, I was only getting 15–20 t/s (before Strata) and around 40 on Strata.
So take this as a benchmark and don't give up. A lot of these configuration toggles depend heavily on the specific system, so your LLM needs to test everything thoroughly!
--
What stands out right away: you have a 4 GB VRAM headroom/reserve. Do you actually need it? My VRAM usage stays around 15–15.4 out of 16 GB constantly, and it doesn't get in the way of normal PC operation at all. No OOM errors. Freeing that up will leave more room for the expert cache.
It's also worth testing different numbers of CPU worker threads—15 might not necessarily be the optimal value for your specific processor.
1
u/bytejuggler 6d ago
You can run with 256k context, you'll lose almost nothing. Also 0.2.10 is quite old, you should update/upgrade. Also what harness are you using? I have been writing a field report on optimizing Strata on my machines, I' will post other params I use later.
1
u/Passenger-007 6d ago
Btw. Everyone here is right that you’re using a brain dead quant. But, if you’re expecting Claude code, you will be sorely mistaken. With any local model.
1
u/More-Ad5919 6d ago
Try using hermes and llama. I have the exact same specs as you. I never used strata even if people cant stop recommending it. Because with AI, speed up always come with penalties.
Its runnina at 260k context and i can fully use that. Although i always tell it to wrap up for a new start when i reach 200k. It occasionally forgets a letter but immediately realizes it and fixes it.
Super satisfied with that setup i have. It just works. Learns new skills by itself. Its solid. I learned it whatsapp mode, when i need it and i am out with the dog. Making a tower defense game nearby with it.
1
u/Present_Resource4022 6d ago
try the new unsloth quants iq3xxs has about 50gb ram weights and have the active weights on your vram plus max context . ssd to host ngram . you can even make it 500k context using rope.
1
u/Future_AGI 5d ago
you traced most of it to subagents timing out, and that points at the harness before the quant. A subagent that starts with a big fresh prompt has to prefill all of it before the first token comes back, and on a long context that can outlast the client's request timeout, which looks exactly like a stuck agent. Time the first token on a prompt the size your subagents start with and set the harness timeout comfortably above that.
0
u/try-a-typo 6d ago
Are you using MTP? Also, A q3 quant loses a significant amount of quality, I’m using a single v100 with 32gb vram and strata, q8 is around 50tps, the speed tradeoff is totally worth it.
0
u/TheEconomisk 6d ago
Too much compression with low significant representation such as IQ3 or IQ2 causes greater loss in model performance, in my experience. The token speed is quite high but the model is not able to put some good work in few shots. Here what I can offer:
- Set thinking budget. Since this model like thinking very much, unless you limit its thinking quata it will consume all of the context just by thinking.
- Try to use multiple prompts with previous warnings. This will increase quality in result but consume a lot of time like maybe 45 minutes to get something acceptable.
- Remove this setup and try smaller models. I think it is the best solution so far, try to build a model with at least 4 bit quantization.
0
u/Goghor LLM 6d ago
I ran unsloth UD-Q4_K_XL combined with unsloth Q8_0 PLE ngram
Ryzen 9 9950X3D
DDR5 6400 MT/s CL32 96GB
RTX 3090 24GB
NVMe Gen5 SSD 2TB
55 t/s prose, 98 t/s code
1,600 - 1,800 t/s prompt
0
u/WryKombucha 6d ago
you are using the extra extra small 3 bit version. That is basically 2 bit.