Running Qwen3.6 35B-A3B

the alternatives

Only just means it works, until the day you lengthen the context or open something else. Which is the day you conclude the tool lied to you.

not enough memory

• NVIDIA GeForce RTX 3060 8 GB · 8 GB usable
• NVIDIA GeForce RTX 3070 · 8 GB usable
• NVIDIA GeForce RTX 5060 8 GB (MSI Shadow 2X OC) · 8 GB usable
• No graphics card, 16 GB of RAM · 9.6 GB usable
• NVIDIA GeForce RTX 3080 · 10 GB usable
• NVIDIA GeForce RTX 3060 12 GB · 12 GB usable
• NVIDIA GeForce RTX 4070 · 12 GB usable
• NVIDIA GeForce RTX 5070 12 GB (MSI Shadow 2X OC) · 12 GB usable
• Apple Silicon, 16 GB unified · 12 GB usable
• NVIDIA GeForce RTX 4060 Ti 16 GB · 16 GB usable
• NVIDIA GeForce RTX 4080 · 16 GB usable
• NVIDIA GeForce RTX 5060 Ti 16 GB (MSI Shadow 2X OC Plus) · 16 GB usable
• NVIDIA GeForce RTX 5070 Ti 16 GB (MSI Shadow 3X OC) · 16 GB usable
• Apple Silicon, 24 GB unified · 18 GB usable
• No graphics card, 32 GB of RAM · 19.2 GB usable

if you change the format

4-bit weightswhat almost everyone runs, and what the hardware below is judged against

23.8 GB

8-bit weightsvisibly better on long or precise answers

42.7 GB

16-bit weightsthe model as it was trained, and rarely worth it at home

84.7 GB

Everything above assumes 4-bit weights and a 8k token context. Going up in precision costs memory; shortening the context is the other lever, and the cheaper one when something almost fits. Model details checked on 2026-08-02.

how to actually run it

what this page will not tell you

How many tokens per second you will get. That is a benchmark — it depends on memory bandwidth, on the engine, on the context and on how long the answers are. This site does not invent benchmarks, and everyone who quotes one for your exact setup is guessing.