Can the Apple M3 Ultra run Qwen3.6-35B-A3B?
IT FITS
Yes. 9 of 9 formats evaluated fit in 512 GB, the largest Apple M3 Ultra configuration, at 8,192 tokens. No published file exists for this pair, so every size is rebuilt from the pinned architecture. The best quality that fits is FP16, needing 73.0 GB and running at an estimated 79 tokens per second.
Fitting in memory is not the same as loading. Whether the runtime and version you have supports this architecture and format on this machine has not been tested here.
Find the Apple M3 Ultra: Amazon ↗ · eBay (new and used) ↗Store links may pay us a commission. They never decide which card is suggested — the memory arithmetic does.
How long a conversation. At FP16, this pair holds 262,144 tokens of context — roughly 196,608 words — needing 78.2 GB. That is Qwen's own configured maximum of 262,144 tokens, not the card running out. A larger device does not extend it; a documented RoPE or YaRN extension might, and is a separate question from this one.
By memory configuration
The Apple M3 Ultra is sold with 96, 256 or 512 GB of unified memory, and the amount decides the fit. Each row is the best format that fits in that much at 8,192 tokens, whole model resident.
Every format evaluated
No published file exists for this pair, so every size is rebuilt from the pinned architecture. The Basis column says which is which for each row. Decode and first-token figures are calibrated estimates, not runs on this card.
| Format | Needs | Of 512 GB | Fits | Decode | First token | Basis |
|---|---|---|---|---|---|---|
| FP16 | 73.0 GB | 14% | yes | ~79 tok/s | no comparable peak | size range |
| Q8_0 | 39.3 GB | 8% | yes | ~111 tok/s | no comparable peak | size range |
| Q6_K | 30.6 GB | 6% | yes | ~122 tok/s | no comparable peak | size range |
| Q5_K_M | 26.7 GB | 5% | yes | ~118 tok/s | no comparable peak | size range |
| Q5_0 | 26.1 GB | 5% | yes | ~119 tok/s | no comparable peak | size range |
| Q4_K_M | 23.1 GB | 5% | yes | ~123 tok/s | no comparable peak | size range |
| Q4_0 | 22.0 GB | 4% | yes | ~124 tok/s | no comparable peak | size range |
| Q3_K_M | 19.0 GB | 4% | yes | ~127 tok/s | no comparable peak | size range |
| Q2_K | 15.3 GB | 3% | yes | ~132 tok/s | no comparable peak | size range |
Sized at 8,192 tokens of context with the whole model resident — weights, the KV cache and the runtime reserve, offload off. Speed is only quoted for a format that fits: a rate for a configuration that cannot load is not a fact about anything.
Why the first-token figure is the same on every row
First token is modelled from the arithmetic the prompt requires, and that count does not change with the weight format — which is why it reads the same on every row. Real prefill does vary by format, because a quantized matmul is a different kernel; this model does not capture that, and the figure should be read as an order of magnitude rather than a ranking between formats.
What the labels mean
- published data
- Read from a published source — a file's byte count, a model's configuration or a manufacturer's specification — or exact arithmetic on such values. Not a measurement on a machine.
- reconstructed size
- Weight size reconstructed from the pinned architecture, because no published file exists.
- size range
- Only a lower and an upper bound are claimed for this weight size.
- estimate
- Calculated from sourced inputs by a stated method; an estimate, not a measurement.
This page fixes the context at 8,192 tokens and one device. Batch, concurrent users, KV-cache format, clusters and rental cost are all in the calculator, already set to this pairing.
Qwen3.6-35B-A3B’s architecture is read from its publisher’s own config.json at a pinned revision, and the Apple M3 Ultra’s 512 GB and 800 GB/s come from the manufacturer’s specification. How far each figure can be trusted is published, per format and worst case included, on the accuracy scorecard.
Building this into your own product? A free API key returns exactly these figures, and the widget puts this answer on a product page with one script tag.
Use this answer in your own product
curl -s https://llmbottleneck.com/v1/analyze \
-H "Authorization: Bearer $LLMB_KEY" -H "content-type: application/json" \
-d '{"model":"qwen-qwen3-6-35b-a3b","quantization":"FP16","context":8192,"hardware":"apple-m3-ultra"}'Same engine, same evidence, every field sourced. Free key in one step →
<script src="https://llmbottleneck.com/widget.js" data-model="qwen-qwen3-6-35b-a3b" data-quantization="FP16" data-hardware="apple-m3-ultra" data-context="8192"></script>
No key needed. Unbranded, with your own buy button, on Pro and Business →