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-API] XCP: dom0 scalability

To: "'xen-api@xxxxxxxxxxxxxxxxxxx'" <xen-api@xxxxxxxxxxxxxxxxxxx>, "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-API] XCP: dom0 scalability
From: Dave Scott <Dave.Scott@xxxxxxxxxxxxx>
Date: Fri, 8 Oct 2010 20:54:25 +0100
Accept-language: en-US
Acceptlanguage: en-US
Cc:
Delivery-date: Fri, 08 Oct 2010 12:54:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: ActnIpvfd1BrqbYvSkuIwjPzfnFWYA==
Thread-topic: XCP: dom0 scalability
Hi,

I've added a draft of a doc called "the dom0 capacity crunch" to the wiki:

http://wiki.xensource.com/xenwiki/XCP_Overview?action=AttachFile&do=get&target=xcp_dom0_capacity_crunch.pdf

The doc contains a proposal for dealing with ever-increasing dom0 load, 
primarily by moving the load out of dom0 (stubdoms, helper domains etc) and, 
where still necessary, tweaking the number of dom0 vcpus. I think this is 
becoming pretty important and we'll need to work on this asap.

Comments are welcome.

Cheers,
Dave

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

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