All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Kirstein <xenlist@custom.ray.net>
To: xen-devel@lists.xensource.com
Subject: Re: Supported #of CPUs/VMs per CPUs
Date: Fri, 22 Sep 2006 02:34:04 +0200	[thread overview]
Message-ID: <20060922023404.A22163@web.ray.net> (raw)
In-Reply-To: <de76405a0609180640p2198bb92yd088a4fbb9c91a0e@mail.gmail.com>; from dunlapg@umich.edu on Mon, Sep 18, 2006 at 09:40:14AM -0400

Hi,

> There is no maximum number of domains per cpu.  The maximum number of
> domains *per machine* (regardless of the # of CPUs) depends on the
> amount of resources available, mainly memory.
> I've never tried to max out the numer if idle domains in Xen, but
> in general, the answer is quite a bit.
I did try it out (see "maximum Number of DomUs" posting a few months
back) on a 16 GB Quad-Opteron, and was surprised hitting a limit
way before I used up all my memory, at about 107 DomUs. Xen has a
private heap of 16MB and each Domain needs some memory there, so
(possibly depending of what else is stored there) at about 100 DomUs
that's it.

Sure, not a real problem (there are few usefull szenarios in which
one would want 100 DomUs on one host), but worth mentioning IMHO...
Or did something change in this respect?

(:ul8er, r@y

  reply	other threads:[~2006-09-22  0:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15 17:18 Supported #of CPUs/VMs per CPUs whit
2006-09-18  9:22 ` Keir Fraser
2006-09-18 12:04   ` whit
2006-09-18 12:23     ` Keir Fraser
2006-09-18 14:23       ` Puthiyaparambil, Aravindh
2006-09-18 14:45         ` Keir Fraser
2006-09-18 13:40     ` George Dunlap 
2006-09-22  0:34       ` Florian Kirstein [this message]
2006-09-22  9:02         ` Petersson, Mats
2006-09-22 13:45           ` George Dunlap 
2006-09-18 12:17   ` Daniel P. Berrange
2006-09-18 12:29     ` Keir Fraser

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=20060922023404.A22163@web.ray.net \
    --to=xenlist@custom.ray.net \
    --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.