|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] Is anyone using the credit scheduler "cap" functionality
To: |
Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx> |
Subject: |
RE: [Xen-devel] Is anyone using the credit scheduler "cap" functionality? |
From: |
"Santos, Jose Renato G" <joserenato.santos@xxxxxx> |
Date: |
Wed, 21 Jan 2009 17:11:39 +0000 |
Accept-language: |
en-US |
Acceptlanguage: |
en-US |
Cc: |
"Turner, Yoshio" <yoshio_turner@xxxxxx>, Wei Zheng <wzheng@xxxxxxxxxxxxxx>, Ricardo Bianchini <ricardob@xxxxxxxxxxxxxx> |
Delivery-date: |
Wed, 21 Jan 2009 09:12:59 -0800 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<d8912bb4-bfd5-4b6c-bdca-ac43bf845214@default> |
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: |
<de76405a0901201109q522cbbc1ldc9567047fdaba5@xxxxxxxxxxxxxx> <d8912bb4-bfd5-4b6c-bdca-ac43bf845214@default> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Thread-index: |
Acl7Pm9q+96UYXJNQ4GFFn6IvNS8OQAqe2vw |
Thread-topic: |
[Xen-devel] Is anyone using the credit scheduler "cap" functionality? |
I would add another use for cap.
Sometimes it is usefull to understand how a domain behaves as a function of the
amount of CPU that is allocated to it. For example when deciding how many
applications can be consolidated on a server you may want to run some tests
with specific benchmarks controling the exact amount of CPU allocated to the
domain running the application. This allow you to predict how a domain will
behave when the amount of CPU is limited due to sharing the CPU with other
domain.
The cap is very useful for this scenario. In fact, Rutgers University and HP
Labs are working on a Research Project (JustRunIt) that uses the CAP
functionality of the scheduler to test and characterize a domain behavior as a
function of the allocated CPU.
I would be very disappointed if the CAP functionality was removed from Xen
scheduler
Renato
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Dan Magenheimer
> Sent: Tuesday, January 20, 2009 12:33 PM
> To: George Dunlap; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-devel] Is anyone using the credit scheduler
> "cap" functionality?
>
> IIRC, the cap functionality is useful primarily for
> application licensing, e.g. to ensure that an app licensed
> for 2 cpus never gets more than 2 cpus, even if all other
> cpus are idle.
> I suppose it could also be used by a webhosting provider to
> create similar limits to allow selling of an added-value tier
> (e.g. "uncapped", kind of a poor man's cloud computing).
>
> Given that, I'd say this is a much too restricted forum
> (primarily developers) to ask and, even if it's not being
> used today, pulling it out seems premature unless there's a
> *really* good reason.
>
> My two cents,
> Dan
>
> > -----Original Message-----
> > From: George Dunlap [mailto:George.Dunlap@xxxxxxxxxxxxx]
> > Sent: Tuesday, January 20, 2009 12:09 PM
> > To: xen-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: [Xen-devel] Is anyone using the credit scheduler "cap"
> > functionality?
> >
> >
> > I'm in the process of revising the credit scheduler design, and I'd
> > like to know how important it is to maintain the "cap"
> functionality
> > of the credit scheduler. If you use it, or know of someone
> who does,
> > could you let me know?
> >
> > If you don't know what it is, you probably aren't using it. :-)
> >
> > Peace,
> > -George
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> >
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|