By Web Asset House · data reviewed 2026-10-22
Compare an exact configuration, not a product-family headline. These systems combine different processors, memory designs, and software backends. The table uses maker specifications from the dataset; it does not claim equivalent inference performance or hands-on testing.
| Configuration | Capacity | Listed bandwidth | Approximate USD reference | Source |
|---|---|---|---|---|
| Mac Studio M5 Max (32-core GPU) 36GB | 36 GiB | 460 GB/s | $2,499Apple US advertised system price; 512GB SSD | Maker specifications |
| Mac Studio M5 Max (40-core GPU) 64GB | 64 GiB | 614 GB/s | Price not verifiedQuote needed: total price unavailable | Maker specifications |
| Mac Studio M5 Max (40-core GPU) 128GB | 128 GiB | 614 GB/s | Price not verifiedQuote needed: total price unavailable | Maker specifications |
| Mac Studio M5 Ultra (30-core CPU / 64-core GPU) 96GB | 96 GiB | 1200 GB/s | Price not verifiedQuote needed: total price unavailable | Maker specifications |
| Mac Studio M5 Ultra (36-core CPU / 80-core GPU) 256GB | 256 GiB | 1200 GB/s | Price not verifiedQuote needed: total price unavailable | Maker specifications |
| Mac Studio M5 Ultra (36-core CPU / 80-core GPU) 512GB | 512 GiB | 1200 GB/s | Price not verifiedQuote needed: total price unavailable | Maker specifications |
| Mac Studio (2025) M4 Max (32-core GPU) 36GB | 36 GiB | 410 GB/s | Price not verifiedQuote needed: total price unavailable | Maker specifications |
| Mac Studio (2025) M4 Max (40-core GPU) 64GB | 64 GiB | 546 GB/s | Price not verifiedQuote needed: total price unavailable | Maker specifications |
| Mac Studio (2025) M4 Max (40-core GPU) 128GB | 128 GiB | 546 GB/s | Price not verifiedQuote needed: total price unavailable | Maker specifications |
| Mac Studio (2025) M3 Ultra (28-core CPU / 60-core GPU) 96GB | 96 GiB | 819 GB/s | Price not verifiedQuote needed: total price unavailable | Maker specifications |
| Mac Studio (2025) M3 Ultra (32-core CPU / 80-core GPU) 256GB | 256 GiB | 819 GB/s | Price not verifiedQuote needed: total price unavailable | Maker specifications |
| AMD Ryzen AI Halo, Ryzen AI Max+ 395, 128GB | 128 GiB | 256 GB/s | Price not verifiedQuote needed: total price unavailable | Maker specifications |
| NVIDIA DGX Spark 128GB / 4TB | 128 GiB | 273 GB/s | $6,950NVIDIA advertised system price; out of stock | Maker specifications |
Read the memory figure carefully
Installed memory, GPU-addressable memory, and the amount left after system reservations are different quantities. Our default usable-memory fraction makes the reservation visible. Firmware and driver allocation limits still need verification on the exact machine.
Do not compare peak compute to token generation
A peak AI-operations figure and an autoregressive generation benchmark measure different things. Our speed estimate is a bandwidth proxy at batch size one. It does not predict prompt-processing throughput, training, image generation, or simultaneous users.
Choose the software first
Verify that your intended model and quantization run on the platform’s supported backend. Manufacturer benchmark formats such as FP4 and FP8 should not be treated as interchangeable with a recorded GGUF Q4_K_M file. See the methodology for published benchmark context and estimator limitations.
Primary sources
- Ollama: memory, context, local and cloud behavior
- llama.cpp: supported build backends
- Hugging Face: GGUF documentation
Questions, answered.
Does the largest capacity mean the highest generation speed?
No. Capacity determines whether the workload may fit. Bandwidth, compute, software, quantization, and workload affect speed.
Are manufacturer benchmarks directly comparable?
Only when model, quantization, runtime, context, batch size, and measurement method match. Otherwise they provide context rather than validation.