From: George Dunlap <george.dunlap@citrix.com>
To: David Xu <davidxu06@gmail.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: performance of credit2 on hybrid workload
Date: Wed, 25 May 2011 17:18:29 +0100 [thread overview]
Message-ID: <1306340309.21026.8524.camel@elijah> (raw)
In-Reply-To: <BANLkTik9+a64cm6YPgnL0sTaXbEWCqYJcA@mail.gmail.com>
On Mon, 2011-05-23 at 09:15 +0100, David Xu wrote:
> Hi,
>
>
> Xen4.1 datasheet tells that credit2 scheduler is designed for latency
> sensitive workloads. Does it have some improvement on the hybrid
> workload including both the cpu-bound and latency-sensitive i/o work?
> For example, if a VM runs a cpu-bound task burning the cpu and a
> i/o-bound (latency-sensitive) task simultaneously, will the latency be
> guaranteed? And how?
At the moment, the "mixed workload" problem, where a single VM does both
cpu-intensive and latency-sensitive* workloads, has not been addressed
yet. I have some ideas, but I haven't implemented them yet.
* i/o-bound is not the same as latency sensitive. They obviously go
together frequently, but I would make a distinction between them. For
example, an scp (copy over ssh) can easily become cpu-bound if there is
competition for the cpu -- but it is nonetheless latency sensitive. (I
guess to put it another way, a workload which is latency-sensitive may
become i/o-bound if its scheduling latency is too high.)
-George
next prev parent reply other threads:[~2011-05-25 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 8:15 performance of credit2 on hybrid workload David Xu
2011-05-25 16:18 ` George Dunlap [this message]
[not found] ` <BANLkTi=57gDitoq7-T7n9Zh0_ZrCMuxfRg@mail.gmail.com>
[not found] ` <1306401493.21026.8526.camel@elijah>
2011-06-01 0:55 ` David Xu
2011-06-01 9:31 ` George Dunlap
2011-06-07 19:28 ` David Xu
2011-06-08 10:36 ` George Dunlap
2011-06-08 21:43 ` David Xu
2011-06-09 13:34 ` George Dunlap
2011-06-09 19:50 ` David Xu
2011-06-13 16:52 ` David Xu
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=1306340309.21026.8524.camel@elijah \
--to=george.dunlap@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=davidxu06@gmail.com \
--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).