All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Gordan Bobic <gordan@bobich.net>
Cc: lars.kurth@xen.org, xen-devel@lists.xen.org
Subject: Re: Xen 4.2.2 / KVM / VirtualBox benchmark on Haswell
Date: Thu, 11 Jul 2013 12:53:48 +0200	[thread overview]
Message-ID: <1373540028.12772.31.camel@Solace> (raw)
In-Reply-To: <dce25df4538ee4ddd0337067c3234b12@mail.shatteredsilicon.net>


[-- Attachment #1.1: Type: text/plain, Size: 1258 bytes --]

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...

Anyway, if you do anything like this, please, do let us know here (and,
please, Cc me :-P).

Thanks and 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

  reply	other threads:[~2013-07-11 10:53 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 [this message]
2013-07-11 16:23     ` George Dunlap
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=1373540028.12772.31.camel@Solace \
    --to=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 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.