4× RTX 5090
$1.07per hour
- Speed
- ~1172 tok/sFaster than you read
- Per million tokens
- $0.25
Vast.ai · Marketplace · 99.6% reliable
Rent on Vast.aiLowest cost per token at 20+ tok/s
LLM//BOTTLENECK
IT DOES NOT FIT
No. Even Q2_K, the smallest format evaluated, needs 72.4 GB against 64 GB, the largest Apple M1 Max configuration — short by 8.40 GB. No published file exists for this pair, so every size is rebuilt from the pinned architecture.
The Apple M1 Max cannot hold it, but these rented machines hold the whole model. The ones worth choosing between, priced live and billed by the second.
$1.07per hour
Vast.ai · Marketplace · 99.6% reliable
Rent on Vast.aiLowest cost per token at 20+ tok/s
$7.89per hour
RunPod · Secure Cloud
Rent on RunPodHighest speed estimate
Compare all 11 rentable configurations →
Here the rented card is as cheap as the API or cheaper per token ($0.25 per million), and it keeps your data on a machine you control. The API is still the easier start: nothing to set up and nothing to switch off.
No Q4_K_M file of Qwen3.8-Flash-Next is catalogued here, so there is no exact command to vouch for. Start the machine from the llama.cpp server image ghcr.io/ggml-org/llama.cpp:server-cuda and point -hf at a Q4_K_M build from the publisher or a quantizer you trust — search Hugging Face for one. Check its file size against the memory figure on this page before you rent.
Every machine holds the whole model at Q4_K_M and 8,192 tokens of context, no offload. Speeds are this site’s single-stream decode estimates; prices are what each provider’s own API quoted, on-demand, for the whole machine. Vast hosts below 98% measured reliability are left out.
Referral links Vast.ai, RunPod and Novita pay us a share of what you spend if you sign up through these buttons. It costs you nothing, and it never decides an order or a recommendation: both are computed from the live price and the speed, and options that pay us nothing are listed and recommended on the same terms. How we rank
The models nearest to Qwen3.8-Flash-Next — same lab first, then closest in size — that the Apple M1 Max holds whole at the standard format and runs at a usable speed. Nearest in size is not the same as equally good; compare them on the task you care about.
The Apple M1 Max is sold with 32 or 64 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.
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 64 GB | Fits | Decode | First token | Basis |
|---|---|---|---|---|---|---|
| FP16 | 361.3 GB | 564% | short by 297.3 GB | does not run | — | size range |
| Q8_0 | 192.5 GB | 301% | short by 128.5 GB | does not run | — | size range |
| Q6_K | 148.9 GB | 233% | short by 84.9 GB | does not run | — | size range |
| Q5_K_M | 129.7 GB | 203% | short by 65.7 GB | does not run | — | size range |
| Q5_0 | 126.7 GB | 198% | short by 62.7 GB | does not run | — | size range |
| Q4_K_M | 111.6 GB | 174% | short by 47.6 GB | does not run | — | size range |
| Q4_0 | 105.9 GB | 165% | short by 41.9 GB | does not run | — | size range |
| Q3_K_M | 91.1 GB | 142% | short by 27.1 GB | does not run | — | size range |
| Q2_K | 72.4 GB | 113% | short by 8.40 GB | does not run | — | 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.
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.
2 of the same card, tensor parallel, holds it at Q2_K. Often cheaper than one larger card, and it is the option most sizing tools never mention.
80 GB holds it at Q2_K.
80 GB holds it at Q2_K.
80 GB holds it at Q2_K.
Keeping some layers on the host lets it load at all, at a large cost in speed. The calculator sizes the split and prices it.
The full list is on the Apple M1 Max page.
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.
Open in the calculator →Everything the Apple M1 Max runsBest models for 64 GB
Qwen3.8-Flash-Next’s architecture is read from its publisher’s own config.json at a pinned revision, and the Apple M1 Max’s 64 GB and 400 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.
curl -s https://llmbottleneck.com/v1/analyze \
-H "Authorization: Bearer $LLMB_KEY" -H "content-type: application/json" \
-d '{"model":"qwen-qwen3-8-flash-next","quantization":"Q2_K","context":8192,"hardware":"apple-m1-max"}'Same engine, same evidence, every field sourced. Free key in one step →
<script src="https://llmbottleneck.com/widget.js" data-model="qwen-qwen3-8-flash-next" data-quantization="Q2_K" data-hardware="apple-m1-max" data-context="8192"></script>
No key needed. Unbranded, with your own buy button, on Pro and Business →