From: Markus Frank <m.frank@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server/pve-manager v1 0/2] add virtio-vga-gl Vulkan (venus) support
Date: Mon, 10 Nov 2025 16:30:17 +0100 [thread overview]
Message-ID: <6f7c7e01-e7b0-467e-8f28-3c1c88583f4a@proxmox.com> (raw)
In-Reply-To: <34ee1ade-1fe2-42e1-8646-5103b9947588@proxmox.com>
On 2025-11-10 14:54, Thomas Lamprecht wrote:
> Am 10.11.25 um 12:40 schrieb Markus Frank:
>> To get an overview of the performance, see the benchmark below.
>>
>> supertuxkart (1.5) benchmark (default settings, vulkan, 1024x768):
>>
>> Host result (Granite Ridge integrated GPU):
>> * Total frame count: 8488
>> * Total profiling time (ms): 38139
>> * Steady FPS: 92
>> * Mostly stable FPS: 137
>> * Typical FPS: 194
>>
>> VM (host, 4 core, 8GiB) with venus (hostmem=8192M) result:
>> * Total frame count: 3321
>> * Total profiling time (ms): 38130
>> * Steady FPS: 58
>> * Mostly stable FPS: 75
>> * Typical FPS: 86
>>
>
> Comparing with a benchmark in the VM with other displays would be also nice.
> Most interesting would be the default (vga IIRC) and qxl (SPICE).
I did, but I do not think the results are really comparable because all current display types use vulkan software rendering, which performs really badly.
See below:
VM virtio-gl (Vulkan, without venus, llvmpipe software rendering):
* Total frame count: 762
* Total profiling time (ms): 260786
* Steady FPS: 1
* Mostly stable FPS: 2
* Typical FPS: 2
To make a more meaningful comparison, it would be better to use OpenGL with virtio-gl.
This is the result I got in the same VM with virtio-gl and a similar supertuxkart benchmark using OpenGL instead of Vulkan:
VM virtio-gl (OpenGL, virgl):
* Total frame count: 2940
* Total profiling time (ms): 38128
* Steady FPS: 35
* Mostly stable FPS: 54
* Typical FPS: 77
OpenGL also requires software rendering with VGA and QXL.
vga (OpenGL, software rendering):
* Total frame count: 762
* Total profiling time (ms): 73867
* Steady FPS: 7
* Mostly stable FPS: 8
* Typical FPS: 10
qxl (OpenGL, software rendering):
* Total frame count: 762
* Total profiling time (ms): 75797
* Steady FPS: 7
* Mostly stable FPS: 8
* Typical FPS: 9
>
>> This benchmark showed no significant differences in performance between
>> the various memory window sizes for venus.
>
> I probably would not expose them then for now.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-11-10 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 11:25 Markus Frank
2025-11-10 11:25 ` [pve-devel] [PATCH qemu-server v1 1/2] virtio-vga-gl: add " Markus Frank
2025-11-10 14:27 ` Thomas Lamprecht
2025-11-11 11:06 ` Markus Frank
2025-11-10 11:25 ` [pve-devel] [PATCH pve-manager v1 2/2] ui: qemu: add Vulkan option in DisplayEdit Markus Frank
2025-11-10 14:30 ` Thomas Lamprecht
2025-11-10 13:54 ` [pve-devel] [PATCH qemu-server/pve-manager v1 0/2] add virtio-vga-gl Vulkan (venus) support Thomas Lamprecht
2025-11-10 15:30 ` Markus Frank [this message]
2025-11-13 15:13 ` Dominik Csapak
2025-11-13 16:21 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6f7c7e01-e7b0-467e-8f28-3c1c88583f4a@proxmox.com \
--to=m.frank@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox