From: Dario Faggioli <dario.faggioli@citrix.com>
To: Sisu Xi <xisisu@gmail.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: VCPU migration overhead conpensation ?
Date: Wed, 10 Apr 2013 08:53:58 +0200 [thread overview]
Message-ID: <1365576838.2934.7.camel@Abyss> (raw)
In-Reply-To: <CAPqOm-pxX+qoZEovjXPztmUYFm7EUA+fhUMpwOy98XppHMmRXA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1715 bytes --]
On mer, 2013-04-10 at 06:44 +0100, Sisu Xi wrote:
> Hi, Dario:
>
Hi! :-)
> I am also performing some overhead measurement for the scheduler. If a
> VCPU is migrated from one core to another, the overhead is around 2
> microseconds on my machine, which is much less than what is set in
> Credit2 (50 microseconds).
>
Ok, and, finally, how did you decide to measure this? I mean, what is it
that you are doing for coming up with that 2us value?
When I was doing research on task scheduling, in "plain" OS, not
hypervisors, I remember having setup something like this: you take a
task (or a set of them), performing a known computation on a certain
CPU, and you measure how long it takes. After that, you force a
migration to another CPU, and keep monitoring the duration of the
computation. Well, the first samples that you get right after the
migration, gives you an idea of the overhead caused by the migration
itself.
Of course, you can/should try different kind of migrations, i.e., across
cores (i.e., with a lot of shared caches), across sockets, etc.
It is an indirect method, but the nice thing is you can use real
programs and inspect the effect of migration on real workloads (e.g., a
video player playing the same video).
Of course, we have one more "layer of indirection" here (the vCPUs), but
I guess we can think of something... So, again, I'm curious, how are you
measuring it?
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
next prev parent reply other threads:[~2013-04-10 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 21:16 VCPU migration overhead conpensation ? Sisu Xi
2013-04-09 1:46 ` Dario Faggioli
2013-04-10 5:44 ` Sisu Xi
2013-04-10 6:53 ` Dario Faggioli [this message]
2013-04-10 8:21 ` George Dunlap
2013-04-10 8:25 ` Dario Faggioli
2013-04-10 18:58 ` Sisu Xi
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=1365576838.2934.7.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=xisisu@gmail.com \
/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.