Ryzen AI Max+ 395 LLM Inference: Specs, Bandwidth, Reality

Ryzen AI Max+ 395: the spec sheet, not the hype

AMD's Ryzen AI Max+ 395 — the flagship "Strix Halo" chip — pairs 16 Zen 5 cores (32 threads) with a Radeon 8060S integrated GPU built on RDNA 3.5 with 40 compute units, an XDNA 2 NPU rated at 50 TOPS, and up to 128GB of unified LPDDR5X-8000 memory on a 256-bit bus, for roughly 256GB/s of peak bandwidth (per AMD's official spec sheet). None of that is unusual for a high-end mobile/APU part on paper. What is unusual is the memory: a single pool, shared between CPU and GPU, large enough to hold a quantized 70B-parameter model without touching a discrete GPU.

That's the entire reason this chip shows up in local-LLM conversations. Discrete consumer GPUs top out around 16-24GB of VRAM; a 70B model at 4-bit quantization needs roughly 40GB just to load. Strix Halo sidesteps that ceiling by giving the GPU access to system memory instead of a fixed VRAM budget — the tradeoff is that "system memory" bandwidth, even at LPDDR5X-8000 speeds, is well below what a dedicated GPU's on-package VRAM delivers.

Core specs at a glance

Source: AMD's official Ryzen AI Max+ 395 product page.

Why unified memory matters more than raw compute here

LLM token generation is typically memory-bandwidth-bound, not compute-bound — for each token, the accelerator has to stream the full set of active weights through memory. That means the practical ceiling on inference throughput tracks memory bandwidth far more closely than it tracks TFLOPs on a spec sheet. Strix Halo's ~256GB/s is a large step up from a typical desktop's dual-channel DDR5 (usually well under 100GB/s), but it's still a fraction of what a dedicated data-center or high-end workstation GPU offers on its own VRAM. The result is a chip that can hold far larger models than any consumer discrete GPU, but generates tokens more slowly per parameter than a GPU with dedicated high-bandwidth memory would, once a model actually fits in both.

In practice that makes the Ryzen AI Max+ 395 most compelling for two specific cases: running models that are simply too large to fit on a 16-24GB consumer GPU at all (large MoE models, 70B+ dense models), and running several small-to-mid models concurrently without VRAM contention. It's a weaker choice if the target model already fits comfortably in 16-24GB, where a discrete GPU with faster dedicated memory will out-generate it.

Software stack: Vulkan first, ROCm catching up

llama.cpp's Vulkan backend was the first reliable way to run models on Strix Halo's iGPU, since it doesn't depend on AMD's compute stack recognizing the specific GPU architecture. Official ROCm support for Strix Halo's gfx1151 architecture landed in a subsequent ROCm release, per AMD's ROCm project release notes on GitHub — until that shipped, community members largely relied on Vulkan or third-party builds. Anyone evaluating this chip for LLM work should check current ROCm compatibility tables before assuming full driver support out of the box, and expect the software stack to still be maturing relative to CUDA on Nvidia or Metal on Apple Silicon.

Community members tracking local-inference performance on Strix Halo hardware post ongoing results on r/LocalLLaMA — that's the most current source for real-world tokens-per-second numbers on specific quantizations, since actual throughput varies heavily by model architecture, context length, quantization format, and which backend (Vulkan vs ROCm) is in use. Treat any single reported number as a snapshot of one config, not a universal figure for the chip.

Where you can actually buy it

The Ryzen AI Max+ 395 isn't sold as a standalone retail CPU — it's an integrated SoC that ships soldered into mini-PCs and a handful of premium laptops. Configurations with the full 128GB memory pool are the ones relevant to large-model inference; lower-memory SKUs (the non-Plus Ryzen AI Max variants) top out well below what's needed for large quantized models.

Pricing on 128GB configurations from these vendors has generally sat well above equivalent-memory discrete-GPU builds on a pure dollars-per-GB basis — the premium buys memory capacity and a small form factor, not raw throughput. Check current listings directly, since AI-PC pricing has moved quickly through 2025 and 2026.

The alternative: a traditional AM4/AM5 box

If your model fits inside a 16-24GB discrete GPU's VRAM, a conventional desktop build still generally out-generates Strix Halo on tokens-per-second at a lower total cost, and it gives you a machine that also handles gaming and general desktop work well. SpecPicks' catalog has AM4-era Ryzen chips that fit this budget-dual-duty role — the Ryzen 5 5600X and Ryzen 7 3700X both show up in our Ryzen 5600G vs 5700X always-on LLM server and Ryzen 7 5800X vs 5700X gaming/LLM build comparisons, paired with standard DDR4 kits like a 16GB Crucial DDR4-3200 kit or 8GB Crucial DDR4-3200 module for the system side of the build. For gaming context on that class of CPU, a Ryzen 5 3600 posts roughly 39fps in Cyberpunk 2077, 63fps in Baldur's Gate 3, and 72fps in Starfield (per public GPU benchmark aggregators) — respectable 1080p numbers if the box is doing double duty.

The tradeoff runs the other way once you need a model that simply won't fit in 24GB: at that point a traditional discrete-GPU build either needs multiple GPUs or can't run the model at all, and Strix Halo's 128GB pool becomes the more practical (if slower-per-token) option. Our Ryzen AI Max vs RTX 4060 and Ryzen AI Max+ 395 vs RTX 4070 comparisons dig into that capacity-vs-speed tradeoff in more depth, and Ryzen AI Max vs RTX 40 Series covers the broader gaming-versus-AI positioning question.

For a lower-cost split setup — a small always-on inference box paired with a separate lightweight client — see our Open WebUI on Raspberry Pi 4, inference on an RTX 3060 build, and the budget-focused Ryzen 5 5600G vs Ryzen 7 5700X LLM + gaming build. If you go the discrete-GPU route, our AM4 CPU cooler guide covers keeping a dual-duty AM4 chip cool under sustained inference load.

Who should actually buy this chip

• Buy it if you specifically need to run models larger than ~24GB quantized (large dense 70B+ models, big MoE architectures) on a single, quiet, low-power box, and per-token speed is secondary to being able to run the model at all.
• Skip it if your target models fit comfortably in 16-24GB — a discrete-GPU desktop will generate tokens faster for less money, and gives you a far more capable gaming/general-purpose machine on the side.
• Watch the software stack before buying — confirm current ROCm/Vulkan support for whichever inference engine you plan to run, since driver maturity has been a moving target through the chip's first year on the market.

FAQs

Does the Ryzen AI Max+ 395 support upgradeable RAM? No. Its LPDDR5X memory is soldered to the package at the time of manufacture, so the memory configuration (up to 128GB on flagship SKUs) is fixed at purchase — unlike a traditional desktop build where DDR4/DDR5 kits are swappable.

Can I buy the Ryzen AI Max+ 395 as a standalone CPU? No. It's sold only as part of complete systems — mini-PCs like the Framework Desktop and GMKtec EVO-X2, and select laptops/tablets such as the ASUS ROG Flow Z13 — not as a retail boxed processor.

Is the Ryzen AI Max+ 395 faster than a discrete GPU for LLM inference? It depends entirely on whether the model fits in the discrete GPU's VRAM. For models that fit in 16-24GB, a discrete GPU with dedicated high-bandwidth memory generally generates tokens faster. For models too large for any consumer discrete GPU, Strix Halo's 128GB unified pool lets you run them at all, which a VRAM-limited GPU simply can't do.

What software do I need to run LLMs on Strix Halo? llama.cpp with the Vulkan backend is the most broadly compatible starting point. ROCm support for the chip's gfx1151 GPU architecture has been added in more recent ROCm releases — check current compatibility before assuming full driver support.

How does memory bandwidth affect token generation speed? LLM token generation is largely memory-bandwidth-bound, so throughput tracks a chip's memory bandwidth more closely than its advertised compute (TOPS/TFLOPs) figures. At roughly 256GB/s, Strix Halo's bandwidth sits above typical dual-channel desktop DDR5 but below dedicated GPU VRAM, which is the core tradeoff behind its positioning for local inference.

Citations and sources

• AMD Ryzen AI Max+ 395 official product page
• Framework Desktop product listing
• GMKtec EVO-X2 product listing
• ROCm project release notes, GitHub
• r/LocalLLaMA community discussion

This piece is editorial synthesis based on publicly available information. No independent first-party benchmarking is reported.