From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Massimo Canonico <mex@di.unipmn.it>,
xen-devel@lists.xen.org
Subject: Re: CAP and performance problem
Date: Fri, 07 Jun 2013 06:45:49 +0200 [thread overview]
Message-ID: <51B1657D.10807@ts.fujitsu.com> (raw)
In-Reply-To: <1370527977.18519.275.camel@Solace>
On 06.06.2013 16:12, Dario Faggioli wrote:
> On gio, 2013-06-06 at 15:55 +0200, Massimo Canonico wrote:
>> On 06/06/2013 03:02 PM, Juergen Gross wrote:
>>> Could you try:
>>>
>>> xl vcpu-list; sleep 10; xl vcpu-list
>>>
>>> when the test is running and post the output?
>>>
>>>
>>> Juergen
>>>
>> here we go:
>>
>> [root@csitest ~]# xl vcpu-list; sleep 10; xl vcpu-list
>> Name ID VCPU CPU State Time(s) CPU
>> Affinity
>> Domain-0 0 0 0 --- 23.0 0
>> Domain-0 0 1 0 --- 10.5 0
>> Domain-0 0 2 0 --- 8.5 0
>> Domain-0 0 3 0 r-- 6.8 0
>> rubis-web 1 0 2 r-- 2968.5 2
>> Name ID VCPU CPU State Time(s) CPU
>> Affinity
>> Domain-0 0 0 0 --- 23.0 0
>> Domain-0 0 1 0 r-- 10.6 0
>> Domain-0 0 2 0 --- 8.5 0
>> Domain-0 0 3 0 --- 6.8 0
>> rubis-web 1 0 2 r-- 2973.5 2
>>
> So, rubis-web's vcpu ran for 5 secs, which sounds right. I see why
> Jurgen asked you to do that, but not how he plans to squeeze anything
> more than that from these numbers... Waiting for him to enlighten us
> again! ;-P
Just for the records: I only wanted to be sure the problem isn't in the xen
scheduler. And this seems to be proved by the numbers.
Juergen
--
Juergen Gross Principal Developer Operating Systems
PBG PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28 Internet: ts.fujitsu.com
D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html
next prev parent reply other threads:[~2013-06-07 4:45 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
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 [this message]
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=51B1657D.10807@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=mex@di.unipmn.it \
--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 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).