From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dave Scott <Dave.Scott@eu.citrix.com>
Cc: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>,
"'xen-api@lists.xensource.com'" <xen-api@lists.xensource.com>
Subject: Re: XCP: dom0 scalability
Date: Tue, 12 Oct 2010 16:16:15 -0700 [thread overview]
Message-ID: <4CB4EC3F.8030508@goop.org> (raw)
In-Reply-To: <81A73678E76EA642801C8F2E4823AD219331853A47@LONPMAILBOX01.citrite.net>
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
next prev parent reply other threads:[~2010-10-12 23:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 19:54 XCP: dom0 scalability Dave Scott
2010-10-08 21:07 ` Pasi Kärkkäinen
[not found] ` <2125056086.32686.1286572149217.JavaMail.root@zmbs4.inria.fr>
[not found] ` <2125056086.32686.1286572149217.JavaMail.root-1K8HEDNouDUZX7ca1aelMg@public.gmane.org>
2010-10-08 22:45 ` Re: [Xen-devel] " Thomas.Gazagnaire-MZpvjPyXg2s
[not found] ` <53616.98.113.167.2.1286577908.squirrel-DGBMVjBhIkmHKRXNmLAf3lAUjnlXr6A1@public.gmane.org>
2010-10-11 20:22 ` Dave Scott
2010-10-09 17:38 ` [Xen-API] " George Shuklin
2010-10-12 23:16 ` Jeremy Fitzhardinge [this message]
2010-10-13 8:50 ` Tim Deegan
2010-10-13 15:46 ` Dan Magenheimer
2010-10-13 16:07 ` Tim Deegan
2010-10-13 16:12 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CB4EC3F.8030508@goop.org \
--to=jeremy@goop.org \
--cc=Dave.Scott@eu.citrix.com \
--cc=xen-api@lists.xensource.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.