From: "Jan Beulich" <JBeulich@suse.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
xen-devel@lists.xenproject.org,
Anshul Makkar <anshul.makkar@citrix.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: [PATCH 00/19] Assorted fixes and improvements to Credit2
Date: Mon, 20 Jun 2016 05:53:06 -0600 [thread overview]
Message-ID: <5767F54202000078000F6AB1@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1466423025.19253.43.camel@citrix.com>
>>> On 20.06.16 at 13:43, <dario.faggioli@citrix.com> wrote:
> On Mon, 2016-06-20 at 01:43 -0600, Jan Beulich wrote:
>> >
>> > >
>> > > >
>> > > > On 17.06.16 at 19:32, <dario.faggioli@citrix.com> wrote:
>> > > -------------------------------------|---------------------------------|
>> > > Xen build, high VM load, with noise | Iperf, high VM load, with noise |
>> > > -------------------------------------|---------------------------------|
>> > > runq=core runq=socket | runq=core runq=socket |
>> > > baseline 41.466 30.630 | baseline 20.333 20.633 |
>> > > patched 36.840 29.080 | patched 19.967 21.000 |
>> > > =======================================================================|
>> > Which, summarizing, means:
>> > * as far as Credit2 is concerned, applying this series and using
>> > runq=socket
>> > is what _ALWAYS_ provides the best results.
>> Always? What about the increase on far the right side of the above
>> table fragment? It's not a big change, but anyway.
>>
> Not sure I follow. By 'far the right side' you mean the results of
> "Iperf, high VM load, with noise"?
>
> If yes, the 'patched' and 'runq=socket' element shows the highest
> value, which in this case is a good thing, because this is Iperf and
> the number is the total throughput in Gbps, and the higher it is, the
> better.
Oh, I see. You certainly said so somewhere in the description;
it's not the first time finding lower-is-better numbers right next
to higher-is-better managed to confuse me.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-20 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 17:32 [PATCH 00/19] Assorted fixes and improvements to Credit2 Dario Faggioli
2016-06-17 23:08 ` Dario Faggioli
2016-06-20 7:43 ` Jan Beulich
2016-06-20 11:43 ` Dario Faggioli
2016-06-20 11:53 ` Jan Beulich [this message]
2016-07-08 10:11 ` George Dunlap
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=5767F54202000078000F6AB1@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=anshul.makkar@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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).