From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Marcus Granado <Marcus.Granado@eu.citrix.com>,
Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>,
Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] credit: Change default timeslice to 5ms
Date: Wed, 5 Mar 2014 17:33:40 +0100 [thread overview]
Message-ID: <1394037220.16409.30.camel@Solace> (raw)
In-Reply-To: <1394036976-484-1-git-send-email-george.dunlap@eu.citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1457 bytes --]
On mer, 2014-03-05 at 16:29 +0000, George Dunlap wrote:
> The 30ms timeslice was chosen nearly a decade ago now, with cpu
> "burning" workloads in mind. In the mean time, processors have gotten
> faster and VMEXITs have gotten faster. A timeslice of 30ms has a
> major cost when running latency-sensitive workloads like network or
> audio streaming: getting caught behind just one or two other VMs can
> introduce a processing delay of up to 60ms, and the "round-robin"
> nature of the credit scheduler means this delay may be introduced
> every time the VM yields for periods of time.
>
> The XenServer performance team at Citrix have done extensive testing
> with various timeslices, including 30ms, 10ms, 5ms, and 2ms. None of
> the workloads exhibited any performance degradation with a 5ms
> timeslice.
>
> Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
> ---
> CC: Jan Beulich <jbeulich@suse.com>
> CC: Tim Deegan <tim@xen.org>
> CC: Keir Fraser <keir@xen.org>
> CC: Dario Faggioli <dario.faggioli@citrix.com>
> CC: Marcus Granado <Marcus.Granado@eu.citrix.com>
> ---
>
Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>
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:[~2014-03-05 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 16:29 [PATCH] credit: Change default timeslice to 5ms George Dunlap
2014-03-05 16:33 ` Dario Faggioli [this message]
2014-03-05 17:18 ` David Vrabel
2014-03-05 18:04 ` Dario Faggioli
2014-03-06 12:04 ` George Dunlap
2014-03-06 12:27 ` Dario Faggioli
2014-03-06 10:39 ` Tim Deegan
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=1394037220.16409.30.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=Marcus.Granado@eu.citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@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.