Performance of llama.cpp with Vulkan #10879
Replies: 300 comments 471 replies
|
AMD FirePro W8100
|
|
With the latest updates:
|
|
With FA:
|
|
AMD RX 470
|
|
With FA:
|
|
i got the mining edition 8 gb ran slightly better
build: e288693 (6242) |
|
Here's a rerun with the recent flash attention updates:
|
|
Nice, it seems to help even on Polaris. |
|
It keeps getting better 😄
|
|
ubuntu 24.04, vulkan and cuda installed from official APT packages.
build: 4da69d1 (4351) vs CUDA on the same build/setup
build: 4da69d1 (4351) |
|
Macbook Air M2 on Asahi Linux ggml_vulkan: Found 1 Vulkan devices:
|
|
For the record I think this is slow on the HoneyKrisp side rather than llama.cpp |
|
Can you share how you got vulkan to build on Asahi? I can't seem to get cmake to notice it. |
|
Spoke too soon, got it working! |
|
Gentoo Linux on ROG Ally (2023) Ryzen Z1 Extreme ggml_vulkan: Found 1 Vulkan devices:
|
|
ggml_vulkan: Found 4 Vulkan devices:
|
|
Cool setup! Could you also post the result of 1, 2 and 3 7900 XTX GPUs? You can use only the first GPU with |
|
|
|
For this multi GPU case getting Vulkan to support #6017 pipeline parallelism might help improve the prompt processing speed. |
|
@netrunnereve I updated the commit id in all my result. |
|
build: 0d52a69 (4439) NVIDIA GeForce RTX 3090 (NVIDIA)
AMD Radeon RX 6800 XT (RADV NAVI21) (radv)
AMD Radeon (TM) Pro VII (RADV VEGA20) (radv)
Intel(R) Arc(tm) A770 Graphics (DG2) (Intel open-source Mesa driver)
|
|
@netrunnereve Some of the tg results here are a little low, I think they might be debug builds. The cmake step (at least on Linux) might require |
|
I've added My release numbers for the RX 470 are basically identical to the ones I posted earlier without the flag.
|
|
Maybe not in your case, but some other results are suspiciously low in tg (for example the RTX 3080) |
|
Build: 8d59d91 (4450)
Lack of proper Xe coopmat support in the ANV driver is a setback honestly.
edit: retested both with the default batch size. |
I put my A770 into a Windows PC and gave Intel GPA and vtune a shot: GPA just crashes most of the time, I couldn't get it to trace anything useful. vtune works, but does not support Vulkan. It just shows some high-level metrics in that case, not really useful sadly. |
I did build it with cmake with build type Release. |
|
In that case it's something else, cause it should be performing similarly to my A770. I suspect the mesa version, there was something in newer mesa versions that slowed down tg on Intel. |
|
A750 has 448 CUs, A770 has 512 CUs I think. Personally, I am not worried about tg. I am worried about pp here. The gemm batch quickly saturates my GPU. |
|
Here's something exotic: An AMD FirePro S10000 dual GPU from 2012 with 2x 3GB GDDR5. build: 914a82d (4452)
|
|
Very interesting, and looks like it's pretty close to the W8100 in tg despite being a dual GPU card. Your backend scales pretty well with layer splitting which is why I find it worthwhile to run my RX470 and W8100 together (I end up getting results that are close to the average of both cards).
|
|
Latest arch with For the sake of consistency I run every bit in a script and also build every target from scratch (for some reason kill -STOP -1
timeout 240s $COMMAND
kill -CONT -1
ggml_vulkan: Found 1 Vulkan devices:
ggml_vulkan: 0 = Intel(R) Iris(R) Xe Graphics (TGL GT2) (Intel open-source Mesa driver) | uma: 1 | fp16: 1 | warp size: 32 | matrix cores: none
build: ff3fcab (4459)
This bit seems to underutilise both GPU and CPU in real conditions based on
|
|
Unless you reduce the number of GPU layers, threads and openblas/non-openblas is not gonna make any difference. Try it with ngl 0, then only prompt processing is accelerated using Vulkan, the rest runs on CPU. This is often a good setting for integrated GPUs. |
|
That's something I didn't think about, with
build: ba8a1f9 (4460)
|
|
It seems latest patches has improved the results a bit: ggml_vulkan: Found 1 Vulkan devices:
|
|
A few months later and I get:
build: f3a4b16 (5568) I run it on Linux (Arch with lama.cpp-vulkan-git package compiled by GCC 15). From my tests, only Vulkan backend ( I'm curious why I cannot go over 6 t/s. Is this an issue with the newer llama.cpp version or with my OS configuration? |
|
Intel ARC A770 on Windows:
build: ba8a1f9 (4460) |
Single GPU VulkanRadeon Instinct MI25 ggml_vulkan: 0 = AMD Radeon Instinct MI25 (RADV VEGA10) (radv) | uma: 0 | fp16: 1 | warp size: 64 | matrix cores: none
build: 2739a71 (4461) Radeon PRO VII ggml_vulkan: 0 = AMD Radeon Pro VII (RADV VEGA20) (radv) | uma: 0 | fp16: 1 | warp size: 64 | matrix cores: none
build: 2739a71 (4461) Multi GPU Vulkanggml_vulkan: 0 = AMD Radeon Pro VII (RADV VEGA20) (radv) | uma: 0 | fp16: 1 | warp size: 64 | matrix cores: none
build: 2739a71 (4461) ggml_vulkan: 0 = AMD Radeon Pro VII (RADV VEGA20) (radv) | uma: 0 | fp16: 1 | warp size: 64 | matrix cores: none
build: 2739a71 (4461) Single GPU RocmDevice 0: AMD Radeon Instinct MI25, compute capability 9.0, VMM: no
build: 2739a71 (4461) Device 0: AMD Radeon Pro VII, compute capability 9.0, VMM: no
build: 2739a71 (4461) Multi GPU RocmDevice 0: AMD Radeon Pro VII, compute capability 9.0, VMM: no
build: 2739a71 (4461) Layer split
build: 2739a71 (4461) Row split
build: 2739a71 (4461) Single GPU speed is decent, but multi GPU trails Rocm by a wide margin, especially with large models due to the lack of row split. |
|
What is the power profile for this MI25? Mine is 110W but its running slower than yours on git from today. |
|
Mine defaults to 220w. |
|
AMD Radeon RX 5700 XT on Arch using mesa-git and setting a higher GPU power limit compared to the stock card.
I also think it could be interesting adding the flash attention results to the scoreboard (even if the support for it still isn't as mature as CUDA's).
|
|
There is no Vulkan flash attention support (except with coopmat2 on very new nvidia drivers). What you're measuring here is a CPU fallback. |
|
I see, I was sure about the CPU fallback but didn't know there was no flash attention support at all. |
|
I tried but there's nothing after 1 hrs , ok, might be 40 mins... Anyway I run the llama_cli for a sample eval...
Meanwhile OpenBLAS |
|
Even at below 1t/s |
|
Truth is ... (0.79 tokens per second), 3788.63 ms / 3 tokens So it's not even...it just slower... |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Those results are crazy with respect to PP...double anyone else's results (mine included) with the A770. What build were you using? |
|
This thread is just for performance of the master branch. |
|
DGX Spark Ubuntu 26 + 610.43.02 driver
build: 657e011 (10001) |
|
Ubuntu 26.04 LTS Note: Two Nvidia P102-100 10GB not benchmarked and limiting GPU to PCIe 8x. llama-2-7b.Q4_0.gguf -fa on,off -ngl 99 --device Vulkan0 load_backend: loaded RPC backend from /llama-b10054/libggml-rpc.so
build: ac2557c (10054) |
|
Ubuntu 26.04 LTS /llama-b10054/llama-bench -m /llama-2-7b.Q4_0.gguf -fa on,off -ngl 99 --device Vulkan2 load_backend: loaded RPC backend from /run/media/czar33/SSD_L2GB_2/llama-b10054/libggml-rpc.so
build: ac2557c (10054) |
|
Intel Arc Pro B70 Running on Ubuntu 26.04 | host: i9 14900K ggml_vulkan: 0 = Intel(R) Graphics (BMG G31) (Intel open-source Mesa driver) | uma: 0 | fp16: 1 | bf16: 1 | warp size: 32 | shared memory: 49152 | int dot: 1 | matrix cores: KHR_coopmat
build: 8452824 (9739) Noteably, these results differ significantly from the Intel B70 results on the scorecard on the original post. Claude Code suggested this could be from the Mesa version. I'm on 26.0.3. Any ideas other ideas on why my results differ? Were the original scorecard results on Windows instead of Linux? |
|
Yeah the scorecard results are on Windows, those drivers are generally much more optimized than the Mesa ones. |
|
AMD Radeon RX 6600 ggml_vulkan: Found 1 Vulkan devices:
build: 86a9c79 (10066) |
|
Intel® Arc™ 140V GPU ggml_vulkan: Found 1 Vulkan devices:
Vulkaninfo:GPU0: build: 178a6c4 (10069) |
|
You are running a vulkan emulation through Windows/WSL2. That's why your numbers are so weak. These are the results for native Vulkan on Windows, same build, same GPU: PS C:\Users\julia\Downloads\llama-b10069-bin-win-vulkan-x64> .\llama-bench.exe -m ..\llama-2-7b.Q4_0.gguf -fa 0,1
build: 178a6c4 (10069) |
|
Thank you for results that I should be getting on my machine. I am bare metal install of Linux install (Debian 13 with kernel 7.0.13+deb13-amd64) see the vulkaninfo for driver information in my post. |
|
Damn, sorry. I saw GPU1 DRIVER_ID_MESA_LLVMPIPE only. |
|
./bin/llama-bench -m ../../llama-2-7b.Q4_0.gguf -ngl 100 -fa 0,1 -sm none -mg 0
build: 91d2fc3 (10073) |
|
AMD Radeon RX 7600
I tried using For Reference:
build: 91f8c9c (10156) |
|
A friend allowed me to test llama.cpp on his new laptop. It's a new Lenovo IdeaPad. Raw numbers below. Vulkan is significantly faster than CPU, especially for prompt processing. ROCm is faster for prompt processing but Vulkan is faster for token generation. This is a general trend I have observed in AMD hardware. Hardware: Software: CPU
build: cb26014 (10310) ROCm
build: cb26014 (10310) Vulkan
build: cb26014 (10310) |
|
Updated for R9700s: Minor variance between the two cards, but...significantly higher performance than last time I ran this (+10%, more or less). |
|
Is your compiler and Vulkan headers up to date? I'm surprised it's reporting |
|
Apologies - I thought I was running from the release version, but it was a feature branch. Here's the current release: Similar story, albeit slightly lower numbers. |
|
NVIDIA CMP 170HX (GA100, sm_80, 64 GB HBM2e) unlocked Mining card (same die gen as A100) ./bin/llama-bench -m llama-2-7b.Q4_0.gguf -ngl 99 -fa 0,1 -p 512,1024,2048,4096,8192,16384,32768 -n 128,256,512,1024,2048
build: 4c1a0af (10430) |
|
Same-machine Vulkan vs ROCm numbers on Strix Halo, for the record. Hardware: Ryzen AI MAX+ 395 / Radeon 8060S (gfx1151) / 128 GB LPDDR5X unified memory, no dedicated VRAM. Ubuntu 24.04.4, kernel 6.17. Measured UMA bandwidth ~230 GB/s. Method: llama.cpp master (2026-08), separate Vulkan (RADV) + ROCm (HIP) builds. llama-bench -p512 -n128 -b512 -t16, plus llama-server /v1/chat/completions max_tokens=200. Single request, serial, ±5%/cell. Decode throughput (tok/s):
On this UMA iGPU, Vulkan wins across the board — bare +2–25%, with MTP +15–21%. On dense 27B the bare gap is small (~3%) but MTP widens it to ~15–20%. Production pick: Vulkan + MTP. Caveat: UMA/shared-memory iGPU only — not comparable to discrete GPUs (RTX 4090 etc.). Full bilingual matrix + reproducible scripts: https://github.com/JJJJJovi/strix-halo-benchmark |
|
(deck@steamdeck llama-b10360)$ ./llama-bench -m ../../models/llama-2-7b.Q4_0.gguf -ngl 100 -fa 0,1
build: 48d22e2 (10360)
|
|
llamacpp version: b10590 llamacpp compiled with; Setting: GPU1 (Core up to 3000mz, vram up to 2650mz, power up to 350W) Setting: GPU1 + GPU0 (Core up to 3000mz, vram up to 2650mz, power up to 350W) tensor + fa 0 don't work, run with fa 1 only Very poor performance of vulkan + tensor split -> but it works and that's something. For comparison gemma 4 31B Q8: Not so bad vulkan + tensor for a larger model, it still doesn't make sense but the progress is nice looking at what was like e.g. a year ago. |
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This is similar to the Apple Silicon benchmark thread, but for Vulkan! We'll be testing the Llama 2 7B model like the other thread to keep things consistent, and use Q4_0 as it's simple to compute and small enough to fit on a 4GB GPU. You can download it here.
Instructions
Either run the commands below or download one of our Vulkan releases. If you have multiple GPUs please run the test on a single GPU using
-sm none -mg YOUR_GPU_NUMBERunless the model is too big to fit in VRAM. If you use RADV please run with the environment variableRADV_PERFTEST=nogttspillas that can fix a bunch of performance issues.Share your llama-bench results along with the git hash and Vulkan info string in the comments. Feel free to try other models and compare backends, but only valid runs will be placed on the scoreboard.
If multiple entries are posted for the same setup I'll prioritize newer commits with substantial Vulkan updates, otherwise I'll pick the one with the highest overall score at my discretion. Performance may vary depending on driver, operating system, board manufacturer, etc. even if the chip is the same. For integrated graphics note that the memory speed and number of channels will greatly affect your inference speed!
Vulkan Scoreboard (Click on the headings to expand the section)
Llama 2 7B, Q4_0, no FA
Llama 2 7B, Q4_0, FA enabled
All reactions