Post

HighVRAM Weekly Digest #1: From 96GB CUDA to 512GB Unified Memory

This week: HighVRAM expanded its large-memory local-AI planning coverage from a 96GB CUDA workstation through 192GB HBM and 512GB shared unified memory. The practical lesson is that capacity opens different model formats, but software support and measured workload behavior still decide whether a system is useful.

Delivery note: this is a web and RSS edition. HighVRAM email signup and delivery are not active, and publication here does not mean an email was sent.

What changed

The new Mac Studio M5 Ultra versus RTX PRO 6000 Blackwell comparison frames a common workstation decision: up to 512GB of shared unified memory with MLX/Metal support, or 96GB of dedicated GDDR7 ECC with a CUDA path. It does not treat memory capacity, bandwidth or AI TOPS as a universal speed ranking.

The dedicated AMD Instinct MI300X 192GB guide adds a third architecture: an OAM datacenter accelerator with 192GB HBM3, 5.3TB/s peak theoretical bandwidth and ROCm requirements. It is not a desktop PCIe card.

What the exact files say

Qwen3.5 artifactComplete filesFirst practical class in this week’s guides
122B-A10B GPTQ-Int478.864GB96GB, with limited file-only headroom
122B-A10B FP8127.163GB192GB dedicated HBM or 256GB shared memory
122B-A10B BF16250.173GB512GB shared memory or supported multi-device placement
397B-A17B GPTQ-Int4235.708GB512GB shared memory or supported multi-device placement
397B-A17B FP8406.152GB512GB shared memory or supported multi-device placement
397B-A17B BF16806.796GB1TB planning class
File totals exclude cache, runtime buffers and other allocations. “Practical class” is a planning starting point, not a benchmark result or compatibility guarantee.

One useful action

If you operate large-model hardware, run one representative workload and submit a reproducible record through the expanded benchmark builder. It now captures multi-device topology, placement strategy, CPU/system-memory offload, batch/concurrency, input modality and separate peak device and system memory. A result with those fields is more useful than an unexplained token-rate screenshot.

Continue reading

Sources and limits

Published October 25, 2026. Hardware specifications are manufacturer-published, and model totals were summed from the cited official repositories. HighVRAM has not independently benchmarked every combination. File fit does not establish compatibility, speed, quality, reliability or value.