From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Xiaodong Yi <xdong.yi@gmail.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Luvalley-2 has been released: running KVM below any operating system
Date: Sun, 19 Apr 2009 15:17:32 +0300 [thread overview]
Message-ID: <49EB165C.1040900@redhat.com> (raw)
In-Reply-To: <49EB1128.9070801@web.de>
Jan Kiszka wrote:
> Avi Kivity wrote:
>
>> Xiaodong Yi wrote:
>>
>>> Hi,
>>>
>>> I've tested the guest Linux using UnixBench 5.1.2. The platform is:
>>> * Intel's Core Due CPU with 2 cores, 2GB RAM
>>> * CentOS 5.2 as the dom0 Linux, i.e., the host Linux for KVM
>>> * CentOS 5.2 as the guest Linux, i.e., the Linux running on the
>>> virtual machine provided by Qemu
>>>
>>> The first set of results is for Luvalley, and the second one is for
>>> KVM. As the result, Luvalley's guest Linux is 20% ~ 30% faster than
>>> KVM's guest! It is very surprise to me. I had through Luvalley's guest
>>> should be the same performance as KVM's.
>>>
>>>
>>>
>> Yes, it is surprising.
>>
>>
>>> Double-Precision Whetstone 12287.7 MWIPS (10.0 s, 2 samples)
>>> Double-Precision Whetstone 2166.3 MWIPS (10.2 s, 2 samples
>>>
>> That's by far the biggest difference. Can you confirm it isn't a typo?
>>
>> If not, then it looks like we have a bug in floating point handling. I
>> don't think this benchmark uses sse.
>>
>>
>
> Even the native Linux numbers are not that high, rather comparable to
> KVM. I suspect Luvalley is fooling the benchmark here...
>
Most likely timing. Likely Luvally guests time runs to slowly, so they
achieve more loops per unit of guest time.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-04-19 12:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 1:53 Luvalley-2 has been released: running KVM below any operating system Xiaodong Yi
2009-04-16 7:13 ` Zhang, Xiantao
2009-04-17 8:54 ` Xiaodong Yi
2009-04-19 11:44 ` Avi Kivity
2009-04-19 11:55 ` Jan Kiszka
2009-04-19 12:17 ` Avi Kivity [this message]
2009-04-20 2:09 ` Xiaodong Yi
2009-05-11 1:33 ` Dong, Eddie
2009-05-11 5:01 ` Xiaodong Yi
2009-04-17 9:09 ` Xiaodong Yi
2009-04-18 20:37 ` Anthony Liguori
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=49EB165C.1040900@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=xdong.yi@gmail.com \
--cc=xiantao.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.