From: Joseph Glanville <joseph.glanville@orionvm.com.au>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel <xen-devel@lists.xensource.com>, yue <ooolinux@163.com>
Subject: Re: how many phy cpus shoulf assigned to dom0
Date: Thu, 5 May 2011 02:18:46 +1000 [thread overview]
Message-ID: <BANLkTikdaFFnRExrGHY+9PRQ=Ls2=N3iMw@mail.gmail.com> (raw)
In-Reply-To: <20110504131854.GB19769@dumpdata.com>
Hi,
Probably a better question for the xen-users list as you will get more
opinions from production users there.
In general it depends on how you are serving storage and network
resources to domUs.
If you are using iSCSI and or software RAID in dom0 to provide storage
for domUs then you should use atleast 2 cores, possibly think about
pinning them or allocating dom0 more credit weight if you are using
the credit sheduler.
Joseph.
On 4 May 2011 23:18, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> On Wed, May 04, 2011 at 02:55:18PM +0800, yue wrote:
>> how many phy cpus shoulf assigned to dom0
>
> That depends. I am actually running with all cpus, but then this is development machines.
> In production I think the idea is one or two - depending on your workload.
>>
>> thanks
>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Kind regards,
Joseph.
Founder | Director
Orion Virtualisation Solutions | www.orionvm.com.au | Phone: 1300 56
99 52 | Mobile: 0428 754 846
prev parent reply other threads:[~2011-05-04 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 6:55 how many phy cpus shoulf assigned to dom0 yue
2011-05-04 13:18 ` Konrad Rzeszutek Wilk
2011-05-04 16:18 ` Joseph Glanville [this message]
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='BANLkTikdaFFnRExrGHY+9PRQ=Ls2=N3iMw@mail.gmail.com' \
--to=joseph.glanville@orionvm.com.au \
--cc=konrad.wilk@oracle.com \
--cc=ooolinux@163.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).