From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: XCP: dom0 scalability Date: Tue, 12 Oct 2010 16:16:15 -0700 Message-ID: <4CB4EC3F.8030508@goop.org> References: <81A73678E76EA642801C8F2E4823AD219331853A47@LONPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <81A73678E76EA642801C8F2E4823AD219331853A47@LONPMAILBOX01.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dave Scott Cc: "'xen-devel@lists.xensource.com'" , "'xen-api@lists.xensource.com'" List-Id: xen-devel@lists.xenproject.org On 10/08/2010 12:54 PM, Dave Scott wrote: > 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. I'm a big fan of disaggregation, but from a performance perspective xenstored seems pretty insignificant. J