Research cutoff: August 8, 2026. Cloud prices change; confirm the linked provider page before starting a long job.
- Start on Runpod for predictable datacenter-GPU smoke tests. For an exact DGX Spark claim, a verified marketplace Spark can now be cheaper: Y's live August 8 offer was USD 0.5096296/hour.
- Use Modal when per-second automation and serverless job orchestration are worth more than the lowest hourly rate.
- Rent a high-host-RAM or multi-GPU machine only to create a quant that cannot be produced on the target box.
- Finish on a physical DGX Spark / Y Computer 128 if the product claim is about GB10 performance. A datacenter GPU proves compatibility, not Spark speed, power, thermals, or ARM64 behavior.
| Finished model | First useful machine | Published price | Use it for |
|---|---|---|---|
| 7–8B Q4 | Runpod RTX A5000, 24GB | $0.27/hour | Harness, prompts, API, tool use |
| 27–35B Q4 | Runpod A40, 48GB | $0.44/hour | Fit and basic quality checks |
| 70B Q4 | Runpod A100 PCIe, 80GB | $1.39/hour | Useful speed and memory curve |
| ~100B Q4 | Runpod RTX PRO 6000, 96GB | $1.99/hour | Large single-GPU fit test |
| 200B-class MoE Q4 | Runpod H200, 141GB | $4.39/hour | Large-checkpoint reproduction |
| Blackwell kernel test | Runpod B200, 180GB | $5.89/hour | Datacenter Blackwell compatibility |
| Exact GB10 / 128GB test | Vast.ai DGX Spark offer | $0.51/hour observed | Final ARM64 fit and Spark performance |
Source: Runpod pricing. Storage and network
charges are separate. Vast.ai marketplace prices and hosts vary, so verify
sys_vendor, product, board, GPU, memory, driver, and architecture before
accepting a result. Y's exact-device capture is
public here.
Modal's comparable published GPU compute is approximately $0.80/hour for L4, $1.95/hour for L40S, $2.50/hour for A100 80GB, $4.54/hour for H200, and $6.25/hour for B200, before separate CPU and RAM charges. Modal is a clean automation layer, not the lowest-cost fixed bench. Source: Modal pricing.
- Pin the upstream repository, model revision, tokenizer, runtime, and CUDA image.
- Save the prompt or workload and the unedited output.
- Record cold-load time, prefill, decode speed, peak memory, and failures.
- Label every unreplicated third-party example Upstream demo.
- Keep the original checkpoint as the baseline.
- Create at least two candidate precisions where practical.
- Compare task quality, not just file size and tokens per second.
- Publish the quant method, calibration data description, hashes, and runtime.
- Treat 1-bit, ternary, and additive models as research builds: they usually need retraining and custom kernels, not merely a lower quantization setting.
- Run three or more repetitions on the exact sellable hardware.
- Test the advertised context length and the realistic default separately.
- Measure power and thermals under a sustained workload.
- Publish the limit: what stops fitting or stops being useful.
Running a finished quant is much cheaper than building it. Standard GGUF conversion can use host RAM; AWQ, GPTQ, NVFP4, activation-aware calibration, and QAT typically need much more accelerator memory.
| Source-model class | Practical build machine | Typical path |
|---|---|---|
| 1–4B | 16–32GB RAM or 12–24GB GPU | Local workstation or low-cost cloud GPU |
| 8–14B | 32–64GB RAM or 24–48GB GPU | A40 / L40S class |
| 27–35B | 80GB GPU or 128GB unified memory | A100 80GB, GH200, or DGX Spark |
| 70–122B | 2 × 80GB GPUs or ≥384GB host RAM | Multi-GPU or large-RAM cloud node |
| 284B+ | Multi-B200/GB300 class | Datacenter quantization job |
For llama.cpp GGUF quantization, the source checkpoint is loaded into host RAM and comparable scratch space is needed. Its reference examples show roughly 32.1GB source → 4.9GB Q4 for 8B, 280.9GB → 43.1GB for 70B, and 1.63TB → 249GB for 405B. Source: llama.cpp quantization documentation.
Useful large-RAM options include Lambda's GH200 instance with 432GB system RAM at $2.29/hour and its 4 × A100 40GB / 900GB RAM instance at $7.96/hour. A 405B-class CPU quant needs closer to a 2TB-RAM node; CoreWeave publishes an 8 × A100 80GB / 2TB configuration at $21.60/hour on demand or $9.65/hour spot. Sources: Lambda instances and CoreWeave pricing.
| Model | What is real now | Y decision |
|---|---|---|
| Liquid LFM2.5-2.6B | Official 1.59GB Q4_0 and 1.67GB Q4_K_M; vendor reports phone inference | Phone proof candidate; LFM commercial license changes above $10M annual revenue |
| Mach-1 Additive 35B | 8.13GB beta checkpoint and custom Apple Silicon engine | Laptop-class lab candidate; not phone-proven and compression recipe is not public |
| Pokee-Isaac 28B | Product announcement and managed service; no public weights found | Cannot independently quantize, bundle, or verify yet |
| DeepSeek V4 Flash | Public 284B/13B-active weights; Y loaded the 97.051 GiB target plus 7.951 GiB sidecar on one DGX Spark | Pro Max proof: 28.29 tok/s fixed generation at a configured 32K context; broader quality testing still required |
Primary sources:
- Liquid LFM2.5-2.6B and official GGUF files
- Mach-1 Additive 35B
- Pokee model documentation
- DeepSeek V4 Flash
NVIDIA's current DGX Spark reference has 128GB unified memory and a $4,699 listed price. It is the correct final bench for GB10 claims. It is unnecessary for the first software test.
Y rented and hardware-verified one marketplace DGX Spark at USD 0.5096296/hour. The machine identified itself as NVIDIA_DGX_Spark / P4242 with an NVIDIA GB10, ARM64, and 127,601,388 kB of OS-visible unified memory. Marketplace hosts still vary: use public weights first, never trust the listing alone, and retain the raw environment and benchmark data.
Sources: NVIDIA DGX Spark listing, DGX Spark porting guide, and CUDA GPU compute capability table.
- Phone: LFM2.5-2.6B Q4_K_M — offline chat, tool call, long document, and thermal soak on an 8GB-class Android phone.
- Solo-company box: Qwen3.6-35B-A3B NVFP4 — coding, browser research, cited document search, and one background image task on a 128GB machine.
- Pro Max acceptance: DeepSeek V4 Flash 0731 + Y IQ3_M DSpark — full private Arena-Hard, near-32K input, concurrency, and sustained power/thermal measurements after the completed fit-and-speed proof.
Each finished run becomes a public proof file with reproducible commands and a one-command Y OS install profile.