From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HFTEp-0003DY-CH for qemu-devel@nongnu.org; Fri, 09 Feb 2007 05:44:19 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HFTEo-0003DQ-1E for qemu-devel@nongnu.org; Fri, 09 Feb 2007 05:44:18 -0500 Received: from mx1.polytechnique.org ([129.104.30.34]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HFTEn-000320-Jq for qemu-devel@nongnu.org; Fri, 09 Feb 2007 05:44:17 -0500 Message-ID: <45CC5063.60504@bellard.org> Date: Fri, 09 Feb 2007 11:43:47 +0100 From: Fabrice Bellard MIME-Version: 1.0 Subject: Re: [Qemu-devel] Xenoppix (KNOPPIX5.1.1 + Xen3.0.4 + QEMU/KVM + HTTP-FUSE) is released References: <20070209.194958.123996617.k.suzaki@aist.go.jp> In-Reply-To: <20070209.194958.123996617.k.suzaki@aist.go.jp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: k.suzaki@aist.go.jp Cc: qemu-devel@nongnu.org Kuniyasu Suzaki wrote: > Dear, > > We released new Xenoppix which is consisted of KNOPPIX5.1.1, Xen3.0.4, QEMU/KVM, > and HTTP-FUSE(stackable/network virtual disk). You can compare Xen(3.0.4 on Linux2.6.16) > and KVM(Release 12 on Linux2.6.19) on the CD-ROM. > [...] > ### Performance > -PI calculation(3 Million-digits) is used to compare. > http://h2np.net/pi/pi_quick_start.tar.gz > We confirmed the performance of kvm was very close to native CPU. However the I/O > was still slow. > | sec | > -----------+-------+---------------------------- > Native CPU| 14.67 | Core2 Duo (T7200) > kvm| 17.90 | IntelVT is effective > kvm(off)| 225.1 | "-no-kvm" is used > qemu(kqemu)| 24.87 | "-kernel-kqemu" isn't used > qemu| 227.1 | "-no-kqemu" is used > Xen(DomU)| 14.68 | > Xen(HVM)| 15.99 | IntelVT is effective > -----------+-------+--------------------------- Hi, Since your benchmark involve a mostly user task, the performance of kqemu must be very close to native CPU time. I suggest you make the following tests to improve your benchmarking of qemu/kqemu: 1) Do not use the clock of the virtualized OS to make the measure. QEMU may have bugs which make it very inaccurate. 2) For best performances with kqemu, it is better to use Linux 2.4 as guest OS (I know this is far from acceptable, but it can help some people to get better performance !). Regards, Fabrice.