WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: performance of credit2 on hybrid workload

To: David Xu <davidxu06@xxxxxxxxx>
Subject: [Xen-devel] Re: performance of credit2 on hybrid workload
From: George Dunlap <george.dunlap@xxxxxxxxxx>
Date: Wed, 25 May 2011 17:18:29 +0100
Cc: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 25 May 2011 09:15:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BANLkTik9+a64cm6YPgnL0sTaXbEWCqYJcA@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BANLkTik9+a64cm6YPgnL0sTaXbEWCqYJcA@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>