From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Massimo Canonico <mex@di.unipmn.it>, xen-devel@lists.xen.org
Subject: Re: CAP and performance problem
Date: Thu, 6 Jun 2013 11:48:49 +0200 [thread overview]
Message-ID: <1370512129.18519.240.camel@Solace> (raw)
In-Reply-To: <51B05030.5000903@eu.citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1992 bytes --]
On gio, 2013-06-06 at 10:02 +0100, George Dunlap wrote:
> Well for one, from the scheduler's perspective, the promise isn't that
> you'll get 50% of the *performance*, but 50% of the *cpu time*. I
> haven't been following the thread terribly closely, but I don't remember
> seeing any xentop or xentrace reports.
>
Yep, I suggested monitoring the vcpu usage, and Massimo reported a
correct 50% utilization for the vcpu in question in xentop.
> The first question is, other
> than performance, do you have any reason to believe that the VM is not
> getting 50% of the cpu time?
>
It correctly gets 50% for me, and for Massimo too, as per what he said
in one other e-mail in the thread.
I agree that it's vcpu utilization and non guest performance we're in
control of, but for a purely CPU bound workload, I guess one can expect
some sort of relationship between the two things, can't him? Besides,
that's right what I get in my tests with Massimo's code. :-)
> At some point while your test is running, could you execute the
> following command in dom0:
>
> xentrace -D -e 0x21000 -T 10 /tmp/test.trace
>
> This will take a 10-second trace of just the scheduling events, placing
> the result in /tmp/test.trace
>
> Then download and build xenalyze from the hg repo here:
>
> http://xenbits.xen.org/ext/xenalyze
>
> and run he following command:
>
> xenalyze -s /tmp/test.trace > /tmp/test.summary
>
> And post the results here?
>
Yes, I suggested trying to produce some traces too. However, having seen
that I get numbers consistent with the expectations, I now wonder what
can interact with the scheduler and make Massimo's results different...
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: 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
prev parent reply other threads:[~2013-06-06 9:48 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
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 [this message]
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=1370512129.18519.240.camel@Solace \
--to=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).