xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>,
	Elena Ufimtseva <elena.ufimtseva@oracle.com>
Cc: Meng Xu <xumengpanda@gmail.com>,
	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: Tue, 1 Mar 2016 23:12:43 +0100	[thread overview]
Message-ID: <1456870363.2959.227.camel@citrix.com> (raw)
In-Reply-To: <1328562453.20160301225130@eikelenboom.it>


[-- Attachment #1.1: Type: text/plain, Size: 1730 bytes --]

On Tue, 2016-03-01 at 22:51 +0100, Sander Eikelenboom wrote:
> Tuesday, March 1, 2016, 9:39:25 PM, you wrote:
> 
> > On Tue, Mar 01, 2016 at 02:52:14PM -0500, Meng Xu wrote:
> > > 
> > > > I dont think I have exhausted all the options here, but it
> > > > looked like
> > > > two last changes did improve performance, but was still not
> > > > comparable to
> > > > HVM case.
> > > > I am trying to find where regression had happened. Performance
> > > > on newer
> > > > kernel (I tried 4.5.0-rc4+) was close or better than HVM.
>
> Just a perhaps silly thought .. but could there be something in the 
> time-measuring that could differ and explain the slightly surprising
> results ?
>
I was about to say the exact same thing. In fact, when I can, I always
try to measure time either from the host, or even from outside, rather
than inside the VM itself.

The host should be fine, although that, in Xen, means measuring in
Dom0, which thing may be affected by virtualization as well so, from
this point of view, outside would be preferrable.

However, measuring from outside (and not even from the host, in certain
case) is not always possible and/or comes with a price.

So, it really depends on the benchmark and on the use case, and in a
bunch of them measuring from the guest is actually fine and/or is what
one wants. However, do at least consider that as an option for the
issue being reported.

Thanks and Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-03-01 22:12 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
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 [this message]
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=1456870363.2959.227.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=commani@gmail.com \
    --cc=elena.ufimtseva@oracle.com \
    --cc=linux@eikelenboom.it \
    --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).