From: Massimo Canonico <mex@di.unipmn.it>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: CAP and performance problem
Date: Tue, 21 May 2013 16:28:04 +0200 [thread overview]
Message-ID: <519B8474.40501@di.unipmn.it> (raw)
In-Reply-To: <1369141576.12423.73.camel@Solace>
Hi Dario,
inline my answers
On 05/21/2013 03:06 PM, Dario Faggioli wrote:
> On mar, 2013-05-21 at 13:54 +0200, Massimo Canonico wrote:
>> Hi George,
>> thanks for your answer.
>>
>> Our physical machine has two processors and two cores for each processors.
>>
>> The virtual machine where our application run has just one VCPU that is
>> pinned to a single core.
>> Instead, dom0 was not pinned to any particular core.
>>
> Ok, and what are you doing in Dom0? I guess almost nothing, is that the
> case?
yes
>
> Also, when inspecting the vCPU utilization, do you see the VM vCPU busy
> up to 100% without cap (or with cap set to 100) and, OTOH, up to 50%
> with cap set to 50?
I have monitored the CPU usage with xentop during the experiment and
I got what you said: my application always use the total amonut of CPU
available.
> Well, looks like a scheduling issue, or, in any case, one where
> something is interacting with the scheduling. Can you perhaps boot Dom0
> so that it uses only 2 or 3 cores (or arrange for that later, e.g., with
> cpupools) and pin the vCPU of the VM on the 4th one?
In my experiments, I pin the vCPU of the VM on one core and other cores
are pinned to Dom0.
[root@csitest ~]# xl vcpu-list
Name ID VCPU CPU State Time(s) CPU
Affinity
Domain-0 0 0 0 --- 383.3 0
Domain-0 0 1 0 -b- 358.1 0
Domain-0 0 2 0 -b- 224.3 0
Domain-0 0 3 0 r-- 256.8 0
rubis-web 1 0 2 -b- 9250.9 2
(rubis-web is, of course, the VM where my application run)
Is this configuration what you meant?
Thanks,
Massimo
>
> I'm not sure what could be going on, but that sounds a reasonable way to
> rule out as much room for interference as possible...
>
> Dario
>
next prev parent reply other threads:[~2013-05-21 14:28 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 9:02 CAP and performance problem Massimo Canonico
2013-05-21 10:41 ` George Dunlap
2013-05-21 10:48 ` George Dunlap
2013-05-21 11:54 ` Massimo Canonico
2013-05-21 13:06 ` Dario Faggioli
2013-05-21 14:28 ` Massimo Canonico [this message]
2013-05-21 14:47 ` Dario Faggioli
2013-05-21 15:26 ` Massimo Canonico
2013-05-22 14:42 ` Massimo Canonico
2013-05-22 15:39 ` Dario Faggioli
2013-05-24 7:48 ` Massimo Canonico
2013-06-04 14:03 ` Massimo Canonico
2013-06-04 14:25 ` Dario Faggioli
2013-06-05 16:50 ` Dario Faggioli
2013-06-05 17:11 ` Dario Faggioli
2013-06-05 17:05 ` Massimo Canonico
2013-06-06 8:37 ` Dario Faggioli
2013-06-06 8:57 ` Massimo Canonico
2013-06-06 9:52 ` Dario Faggioli
2013-06-06 10:39 ` Juergen Gross
2013-06-06 10:44 ` George Dunlap
2013-06-06 12:52 ` Massimo Canonico
2013-06-06 12:58 ` George Dunlap
2013-06-06 13:02 ` Juergen Gross
2013-06-06 13:55 ` Massimo Canonico
2013-06-06 14:12 ` George Dunlap
2013-06-06 14:12 ` Dario Faggioli
2013-06-06 15:27 ` Massimo Canonico
2013-06-06 15:42 ` Dario Faggioli
2013-06-06 15:54 ` Dario Faggioli
2013-06-06 16:27 ` George Dunlap
2013-06-07 7:40 ` Massimo Canonico
2013-06-07 4:45 ` Juergen Gross
2013-06-06 13:03 ` Dario Faggioli
2013-06-06 13:09 ` Massimo Canonico
2013-06-06 9:02 ` George Dunlap
2013-06-06 9:48 ` 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=519B8474.40501@di.unipmn.it \
--to=mex@di.unipmn.it \
--cc=George.Dunlap@eu.citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.