From: George Dunlap <George.Dunlap@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"gilmarlinux@agrovale.com.br" <gilmarlinux@agrovale.com.br>
Subject: Re: Problem Xen 4.0-amd64 + Heartbeat 3.0.3-2 with Debian Squeeze
Date: Wed, 1 Jun 2011 10:21:08 +0100 [thread overview]
Message-ID: <BANLkTimbiG58dG+7JdYCH+9vEqfWJWHEhg@mail.gmail.com> (raw)
In-Reply-To: <1306830624.775.108.camel@zakaz.uk.xensource.com>
On Tue, May 31, 2011 at 9:30 AM, Ian Campbell
<Ian.Campbell@eu.citrix.com> wrote:
> IIRC these sorts of latency sensitive workloads are somewhere that the
> existing credit scheduler doesn't do so well and is something which
> George is looking to address with credit2. His canonical workload of
> this type is audio playback but I suppose heartbeat falls into the same
> broad class. So it might also be worth trying the credit2 scheduler.
It is quite possible to get 50-100ms delays in scheduling with credit1
if the system is fairly busy. What kind of results does xentop
report? You might consider moving to 4.1 and testing the credit2
scheduler.
-George
next prev parent reply other threads:[~2011-06-01 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 0:25 Problem Xen 4.0-amd64 + Heartbeat 3.0.3-2 with Debian Squeeze gilmarlinux
2011-05-28 10:12 ` Ian Campbell
2011-05-28 10:29 ` gilmarlinux
2011-05-30 11:18 ` gilmarlinux
[not found] ` <57342.200.101.20.122.1306617709.squirrel@mail.agrovale.com.br>
2011-05-31 8:30 ` Ian Campbell
[not found] ` <33109.189.73.195.186.1306853111.squirrel@mail.agrovale.com.br>
2011-05-31 14:47 ` Ian Campbell
2011-06-01 9:21 ` George Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-25 15:31 gilmarlinux
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=BANLkTimbiG58dG+7JdYCH+9vEqfWJWHEhg@mail.gmail.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=gilmarlinux@agrovale.com.br \
--cc=xen-devel@lists.xensource.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 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).