Repository navigation
MoE prefill on AMD Radeon 780M (gfx1103) via Vulkan — any real numbers? #27519
Unanswered
realaaronmorris
asked this question in
Q&A
Replies: 1 comment
|
Here are some Vulkan and ROCm numbers from a MINISFORUM UM790 Pro. Numbers are for 0 and 32768 depth so your 20K prompt should land somewhere in between. ROCm - build: c841aee (10687)llama-bench -fa 1 -m gpt-oss-20b-mxfp4.gguf -d 0,32768
llama-bench -fa 1 -m ggml-org-Qwen3.6-35B-A3B-Q8_0.gguf -d 0,32768
Vulkan- build: c841aee (10687)llama-bench -fa 1 -m gpt-oss-20b-mxfp4.gguf -d 0,32768
llama-bench -fa 1 -m ggml-org-Qwen3.6-35B-A3B-Q8_0.gguf -d 0,32768
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hardware: Ryzen 7 7840HS / Radeon 780M (gfx1103), 32GB DDR5-4800, Linux, Mesa RADV.
I'm trying to decide whether a 780M mini-PC is viable as a small always-on inference node, and the deciding factor is MoE prefill, which I can't find a single measurement of on this hardware.
What I've found for dense models on 780M (Gemma 4 12B QAT Q4_0, 7.6GB):
So the iGPU gives ~3x prefill and essentially nothing on decode, which makes sense — decode is bandwidth-bound and the iGPU shares the same DDR5.
My question is about sparse MoE models (Qwen3-30B-A3B, Qwen3.6-35B-A3B, gpt-oss-20b — ~3B active params):
Why prefill specifically: my workload sends ~20k-token prompts. At 150 tok/s prefill that's ~2 minutes; at the ~20 tok/s reported in #15163 it's ~17 minutes, which changes the buying decision entirely.
I've separately measured Qwen3.6-35B-A3B at 45.8 tok/s decode on an M1 Max (Metal), and on CPU-only I measured MoE running slower than a comparable dense model — presumably expert-gather destroying cache locality. I don't know whether that penalty carries over to an iGPU via Vulkan.
Any real numbers, even rough ones, would be appreciated. Happy to run and post benchmarks if I end up buying the hardware.
All reactions