[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Re: [Xen-API] XCP: dom0 scalability


  • To: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: George Shuklin <george.shuklin@xxxxxxxxx>
  • Date: Sat, 09 Oct 2010 21:38:50 +0400
  • Delivery-date: Sat, 09 Oct 2010 10:39:51 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; b=vha9LBJ0uGxPdZ+gCjWrbWs5EbFYIYpcUR2nVioKLyFQPnzpjSYyTkIchYBwkq424g xn3OIhNGT1pZ3Hc6V476RSURP/OqR6e3RkiB7zQymIYwq+CYuJexlPuEolrAGNQnS8i4 GNVwnD5/Gs7Q8gIGCJp+A+Nxt1SGzW7JVQmR8=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

This seems rational, but what about overhead? Every domain will require
own kernel with memory (main concern about memory).

I think, first step shall be splitting xapi to few separate daemons.

Ð ÐÑÐ, 08/10/2010 Ð 20:54 +0100, Dave Scott ÐÐÑÐÑ:
> 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



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.