From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] sdl shared buffer performance measurements
Date: Tue, 09 Sep 2008 16:39:12 +0100 [thread overview]
Message-ID: <48C698A0.1040604@eu.citrix.com> (raw)
Hi all,
I have done some simple tests to measure qemu performances with and
without the shared buffer and sdl.
The tests are really simple: I am just measuring CPU usage and fps on
the host while running the same screensaver on the guest (Windows XP).
The following are the average results:
1)Host 32 bpp, Guest 16 bpp:
SDL shared: CPU 13% average, fps 33
SDL unshared: CPU 16% average, fps 33
2)Host 32 bpp, Guest 24 bpp:
SDL shared: CPU 19% average, fps 33
SDL unshared: CPU 20% average, fps 33
It is seems from the data that sdl has some kind of optimization that
makes qemu perform better converting 16 bpp into 32 bpp compared to the
old vga_template conversion code.
In the 24 bpp case the difference is very small because probably there
isn't much to optimize.
I have to add that I don't think these data are able to fully capture
the advantage given by avoiding the memcpy's, but at least we know that
sdl color conversion routines are not going to make qemu any slower.
Regards,
Stefano
reply other threads:[~2008-09-09 15:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48C698A0.1040604@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).