From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Meng Xu <xumengpanda@gmail.com>
Cc: Hyon-Young Choi <commani@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Question] PARSEC benchmark has smaller execution time in VM than in native?
Date: Mon, 29 Feb 2016 11:06:03 -0500 [thread overview]
Message-ID: <20160229160603.GD28725@char.us.oracle.com> (raw)
In-Reply-To: <CAENZ-+=Jk9arEmvZtEmB1S075QyKPbMxW79P4+SojLVqKqRg-Q@mail.gmail.com>
On Fri, Feb 26, 2016 at 12:02:50AM -0500, Meng Xu wrote:
> Hi,
>
Hey!
CC-ing Elena.
> We are measuring the execution time between native machine environment
> and xen virtualization environment using PARSEC Benchmark [1].
>
> In virtualiztion environment, we run a domU with three VCPUs, each of
> them pinned to a core; we pin the dom0 to another core that is not
> used by the domU.
>
> Inside the Linux in domU in virtualization environment and in native
> environment, We used the cpuset to isolate a core (or VCPU) for the
> system processors and to isolate a core for the benchmark processes.
> We also configured the Linux boot command line with isocpus= option to
> isolate the core for benchmark from other unnecessary processes.
You may want to just offline them and also boot the machine with NUMA
disabled.
>
> We expect that execution time of benchmarks in xen virtualization
> environment is larger than the execution time in native machine
> environment. However, the evaluation gave us an opposite result.
>
> Below is the evaluation data for the canneal and streamcluster benchmarks:
>
> Benchmark: canneal, input=simlarge, conf=gcc-serial
> Native: 6.387s
> Virtualization: 5.890s
>
> Benchmark: streamcluster, input=simlarge, conf=gcc-serial
> Native: 5.276s
> Virtualization: 5.240s
>
> Is there anything wrong with our evaluation that lead to the abnormal
> performance results?
Nothing is wrong. Virtualization is naturally faster than baremetal!
:-)
No clue sadly.
>
> Any suggestion or advice is really appreciated.
>
> Thank you very much for your time on this question!
>
> Best regards,
>
> Meng
>
> [1] http://parsec.cs.princeton.edu/
>
>
> -----------
> Meng Xu
> PhD Student in Computer and Information Science
> University of Pennsylvania
> http://www.cis.upenn.edu/~mengxu/
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-29 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 5:02 [Question] PARSEC benchmark has smaller execution time in VM than in native? Meng Xu
2016-02-29 16:06 ` Konrad Rzeszutek Wilk [this message]
2016-02-29 17:29 ` Meng Xu
2016-02-29 17:59 ` Konrad Rzeszutek Wilk
2016-03-01 13:48 ` Meng Xu
2016-03-01 18:20 ` Elena Ufimtseva
2016-03-01 19:52 ` Meng Xu
2016-03-01 20:39 ` Elena Ufimtseva
2016-03-01 21:51 ` Sander Eikelenboom
2016-03-01 22:06 ` Elena Ufimtseva
2016-03-01 22:12 ` Dario Faggioli
2016-03-02 19:44 ` Meng Xu
2016-03-02 19:41 ` Meng Xu
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=20160229160603.GD28725@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=commani@gmail.com \
--cc=xen-devel@lists.xen.org \
--cc=xumengpanda@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 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).