From: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] kqemu benchmarks versus VMWare 5.0
Date: Thu, 17 Feb 2005 17:06:52 +0100 [thread overview]
Message-ID: <20050217160652.GJ3067@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <cv0u2q$6us$1@sea.gmane.org>
Hi Matthew,
benchmarking integer and floating point operation in a virtual machine
like qemu or vmware doesn't make sense because they are both executed on
the real CPU without any modification of the original code. It should be
the same speed than on the native machine.
Interesting would be numbers where many page faults and context switches
involved. Also havy IO. The test that comes in my mind is compiling a
kernel. It would be interesting if you could paste the numbers for say a
kernel compilation of 2.2.8 with default config.
time ( tar xfz /path/to/kernel.tgz; cd kernel-version; make oldconfig; make bzImage )
Maybe you should meassure the time external because the virtual machine
can loose time ticks. But that would be a good start.
Greetings,
Thomas
prev parent reply other threads:[~2005-02-17 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 2:10 [Qemu-devel] kqemu benchmarks versus VMWare 5.0 Matthew Mastracci
2005-02-17 16:06 ` Thomas Glanzmann [this message]
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=20050217160652.GJ3067@cip.informatik.uni-erlangen.de \
--to=sithglan@stud.uni-erlangen.de \
--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).