From: Dario Faggioli <dario.faggioli@citrix.com>
To: Sisu Xi <xisisu@gmail.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Meng Xu <xumengpanda@gmail.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: memory performance 20% degradation in DomU -- Sisu
Date: Wed, 12 Mar 2014 09:55:37 +0100 [thread overview]
Message-ID: <1394614537.31942.49.camel@Abyss> (raw)
In-Reply-To: <CAPqOm-pQE5oXtgMGcD37-CwJwFjOgcKyu=QLS74Tw1gXofLcjA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1102 bytes --]
On Tue, 2014-03-11 at 15:21 -0500, Sisu Xi wrote:
> by the way, since the same DomU image can get better results on
> another hardware machine, we first assume there are some interference
> from Dom-0.
>
Are you able to share the source of the test program, so that we can try
to reproduce what you're seeing?
> However, when I run the same program in Dom-0, the results looks very
> good, almost the same as native case, just a few out liars. Which
> means the interference form Dom-0 is not causing trouble for dom-0,
> but can interfere with cache program in Dom-U? Is this assumption
> valid?
>
I'm shooting a bit in the dark, but:
- what is Dom0 doing while the DomU is running the workload?
- to what pCPUs are you pinning Dom0's and DomU's vCPUs? Do they
share any level of the cache hierarchy?
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: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-03-12 8:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 22:49 memory performance 20% degradation in DomU -- Sisu Sisu Xi
2014-03-04 23:00 ` Sisu Xi
2014-03-05 17:33 ` Konrad Rzeszutek Wilk
2014-03-05 20:09 ` Sisu Xi
2014-03-05 21:29 ` Gordan Bobic
2014-03-05 22:28 ` Konrad Rzeszutek Wilk
2014-03-06 10:31 ` Gordan Bobic
2014-03-05 22:09 ` Konrad Rzeszutek Wilk
2014-03-11 12:03 ` George Dunlap
2014-03-11 15:46 ` Sisu Xi
2014-03-11 20:21 ` Sisu Xi
2014-03-12 8:55 ` Dario Faggioli [this message]
2014-03-12 16:50 ` Sisu Xi
2014-03-13 10:25 ` George Dunlap
2014-03-12 8:59 ` Dario Faggioli
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=1394614537.31942.49.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xisisu@gmail.com \
--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 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.