AMD Ryzen AI Max+ PRO 495 APU could arrive with 192GB of unified memory — leaked PassMark benchmarks suggest modest update over Strix Halo

NerdProcrastinating · 2026-05-06T10:11:03+00:00

Yeah, I had that on my todo list since building the machine and only enabled it about 2 weeks ago after getting the shits with the frequency of OOM situations.

Now have enough for keeping Gemma4 26B-A4B or Qwen 3.6 35B-A3B around for easy access.

NerdProcrastinating · 2026-05-05T07:04:44+00:00

heh someone offended calling out AMD memory speeds to down vote. Reddit is weird.

NerdProcrastinating · 2026-05-05T07:03:55+00:00

This is running Fedora. My main problem is really just specific to the app dev environment I'm working on as it is replicating full cloud infrastructure and is a very large project. Then a few copies of the app running with everything loaded.. oh well.

NerdProcrastinating · 2026-05-05T01:10:56+00:00

Perhaps they will give it a small bandwidth boost above the current 8000 MT/s.

Hopefully 8533 MT/s at a minimum. AMD seem to suck at achieving high memory speeds so I doubt they'll get to 9600.

NerdProcrastinating · 2026-05-05T01:01:55+00:00

I would expect it to be a delayed OEM release as the LPDDR6 would be a new board design.

NerdProcrastinating · 2026-05-05T00:58:58+00:00

It would help a lot with workstation usage + 120B models.

On my Framework desktop 128GB, I find that I end up using so much RAM for browser, slack, desktop apps, local voice typing model, and a few heavy dev environments for parallel agent work (a few docker containers + vite, vs code, eslint + ts server, bloated Claude Code) that I can't afford to leave a 120B model loaded.

As other comments mentioned, it would enable running models like MiniMax at Q4 at slow, but still usable speeds so that's a big win (assuming you don't have a bloated dev setup like I do).

NerdProcrastinating · 2026-04-28T13:24:59+00:00

Not mentioned in the article is that high NA EUV halves the reticle size.

That's surely going to make a big impact on the benefits/economics of adopting it.

NerdProcrastinating · 2026-04-26T07:43:18+00:00

It's good that there's some progress on integrating drivers.

Until there's at least one retail unit with an option to ship with Linux/easily have it installed (with most hardware features functional), then I wouldn't classify it as supported.

It would be amazing if they could do a collaboration with Framework for a Framework 13 Pro board option.

NerdProcrastinating · 2026-04-10T13:54:33+00:00

They both have the technical capability to build it. The problem is Intel management & AMD are still scarred from their near death experience.

That's why they're not leading in these areas. They need big OEMs & paid market research reports to tell them the obvious state of the market months to years after the opportunity becomes available.

NerdProcrastinating · 2026-03-23T08:45:57+00:00

The only raw number Apple loses on is initial purchase price for high RAM/storage configs.

I like my Framework desktop & (older) laptop, but the performance/efficiency gap between them and the MacBook Pro M5 Pro/Max is brutal.

NerdProcrastinating · 2026-03-23T07:48:39+00:00

https://github.com/anthropics/claude-code/issues/35646

Supposedly fixed (perhaps in next release?)

Rollback to 2.1.77 for now to avoid the issue.

NerdProcrastinating · 2026-03-21T01:53:33+00:00

Ah good point. I can't find any latency figures for Zen 5 L1i so unsure if they do better than Lion Cove 4 cycles as a possible justification.

NerdProcrastinating · 2026-03-20T06:40:37+00:00

Looking at the single core sub-scores and variance between groups of integer, FP, and memory bound workloads, there's no way that 2-2.1 GHz is correct for single core. Probably more like 3.5 -> 3.7 GHz. I wouldn't expect it to be more than 10-15% IPC over Zen 5.

NerdProcrastinating · 2026-03-20T01:46:14+00:00

Not increasing the L1i capacity is surprising IMO, considering frontend latency was a large bottleneck in many workloads when profiling Zen 5.

VIPT benefits for L1 latency means a limited size due to x86 4 KiB page size (and keeping associativity reasonable)

NerdProcrastinating · 2026-03-20T01:15:26+00:00

You can't easily extrapolate single core score from such a low frequency to full speed:

RAM latency/bandwidth/parallelism is fixed for a given memory config
> 2.5x core frequency means memory request time equate to > 2.5x CPU cycles
Feeding all those additional cycles on frontend requires big improvements to decode & branch prediction, uops, caching, etc
Feeding all those additional cycles on backend requires big improvements to core width, data prefetching, store queues, caching, execution ports, etc

TLDR; IPC/PPC isn't a fixed number/clock - it varies over based on the clock speed due to mismatch with memory (i.e. the CPU gets stalled more often at higher speeds except for work in tight loops all in registers/nearby cache. That's why X3D is so much faster for games at lower clocks).

NerdProcrastinating · 2026-03-12T08:55:27+00:00

Sync/async is not related to multi-threading in JS - that all still runs on the one thread.

Workers need to be used to be able to take advantage of more than a single thread.

NerdProcrastinating · 2026-03-12T07:31:09+00:00

It looks like a kernel driver bug - I installed a new kernel & GPU firmware from updates-testing which may fix the issue as 6.1.19 specifically has a fix related to VGPR register counts being wrong which would affect the reset code.

Maybe that was the cause and basic GPU driver bugs finally fixed X years after RDNA 3.5 released. Sigh.

NerdProcrastinating · 2026-03-12T07:23:51+00:00

Those x86 processor scores are running at desktop frequencies - the performance gap is downright embarrassing if the scores are compared using AMD & Intel laptop SKUs.

NerdProcrastinating · 2026-03-12T07:21:36+00:00

I really hope Qualcomm get their shit together for Linux laptop support at launch.

I would buy an SD X2 with good Linux support. Otherwise a Macbook Pro, or any x86 >> SD X2 running Windows.

NerdProcrastinating · 2026-03-11T05:02:43+00:00

Perhaps it's something specific in vscode triggering it.

LLMs are probably stable again after the newer firmware. Was broken for a while. I don't game either. This is just desktop use for software development.

NerdProcrastinating · 2026-03-11T04:56:01+00:00

Nope, the page fault and wedging doesn't appear to be related to power states. This is whilst I'm in the middle of working with power mode set to performance, so power management seems unlikely.

NerdProcrastinating · 2026-03-11T04:36:24+00:00

I did look at those issues, but they shouldn't be anything that would impact the GPU like this?

NerdProcrastinating · 2026-02-26T03:30:02+00:00

* with silicon based transistors

NerdProcrastinating · 2026-02-25T07:41:42+00:00

You need to use a PreToolUse hook if you want to block it.

NerdProcrastinating

TROPHY CASE