From: George Dunlap <George.Dunlap@eu.citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Gordan Bobic <gordan@bobich.net>, Lars Kurth <lars.kurth@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.2.2 / KVM / VirtualBox benchmark on Haswell
Date: Thu, 11 Jul 2013 17:23:46 +0100 [thread overview]
Message-ID: <CAFLBxZYK+0Fxic9FzLR+7V08TDWSisELub_ib1m6jCk2C-e9ug@mail.gmail.com> (raw)
In-Reply-To: <1373540028.12772.31.camel@Solace>
On Thu, Jul 11, 2013 at 11:53 AM, Dario Faggioli
<dario.faggioli@citrix.com> wrote:
> On mar, 2013-07-09 at 16:54 +0100, Gordan Bobic wrote:
>> The process migration overheads are _expensive_
>>
> Indeed!
>
>> - I found that on bare
>> metal pining CPU/RAM intensive processes to cores made a ~20%
>> difference to overall throughput on a C2Q class CPU (no shared caches
>> between the two dies made it worse). I expect 4.3.x will be a
>> substantial improvement with NUMA awareness improvements to the
>> scheduler (looking forward to trying it this weekend).
>>
> Well, yes, something good could be expected, although the actual
> improvement will depend on the number of involved VMs, their sizes, the
> workload they're running, etc.
>
> When I tried to use kernel compile as a benchmark for the NUMA effects,
> it did not turn out that useful to me (and that's why I switched to
> SpecJBB), but perhaps it was me that was doing something wrong...
In my experience, kernel-build has excellent memory locality. One
effect is that the effect of nested paging on TLB time is almostt nil;
I'm not surprised that the caches make the effect of NUMA almost nil
as well.
-George
next prev parent reply other threads:[~2013-07-11 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 15:27 Xen 4.2.2 / KVM / VirtualBox benchmark on Haswell Lars Kurth
2013-07-09 15:40 ` Thanos Makatos
2013-07-09 15:53 ` Ian Murray
2013-07-09 15:56 ` Thanos Makatos
2013-07-09 16:14 ` Gordan Bobic
2013-07-09 16:21 ` Thanos Makatos
2013-07-09 16:26 ` Gordan Bobic
2013-07-09 15:54 ` Gordan Bobic
2013-07-11 10:53 ` Dario Faggioli
2013-07-11 16:23 ` George Dunlap [this message]
2013-07-11 16:27 ` Dario Faggioli
2013-07-11 17:49 ` Gordan Bobic
2013-07-09 16:52 ` Alex Bligh
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=CAFLBxZYK+0Fxic9FzLR+7V08TDWSisELub_ib1m6jCk2C-e9ug@mail.gmail.com \
--to=george.dunlap@eu.citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=gordan@bobich.net \
--cc=lars.kurth@xen.org \
--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).