From: Avi Kivity <avi@redhat.com>
To: Matthieu Olivier <ppmarcel@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Discordant results between UnixBench and nBench
Date: Wed, 23 Dec 2009 14:59:26 +0200 [thread overview]
Message-ID: <4B32142E.4090705@redhat.com> (raw)
In-Reply-To: <c59a6b1d0912230455m1ac27f64k5444d803ddd1c687@mail.gmail.com>
On 12/23/2009 02:55 PM, Matthieu Olivier wrote:
>
> I can only see 4 cores in /proc/cpuinfo.
> According the caract page, there is no hyperthreading.
>
> -> http://ark.intel.com/Product.aspx?id=35130
>
>
In this case the plateau at 4 guests is perfectly understandable.
> I also wonder why the host can still get more CPU ressources over 4
> threads? I guess the purpose of both benchmarks is to overload the
> CPU, so why they can't reach the max?
>
Probably a problem with the benchmark itself.
> I suposed that the FPU was able to handle at least 2 operations the
> same time, or maybe hyperthreading was included, but I can't check the
> first part, and the second isn't true.
>
> Or maybe current x86 processors can handel very well these old
> benchmarks. I can't really say :/
>
No, you should see the same plateau as with kvm. The processor can't
run two threads at once.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-12-23 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 9:43 Discordant results between UnixBench and nBench Matthieu Olivier
2009-12-23 9:53 ` Avi Kivity
2009-12-23 10:35 ` Matthieu Olivier
2009-12-23 10:37 ` Avi Kivity
2009-12-23 12:27 ` Matthieu Olivier
2009-12-23 12:39 ` Avi Kivity
2009-12-23 12:55 ` Matthieu Olivier
2009-12-23 12:59 ` Avi Kivity [this message]
2009-12-23 13:05 ` Matthieu Olivier
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=4B32142E.4090705@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=ppmarcel@gmail.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.