From: Sunil Mushran <sunil.mushran@oracle.com>
To: Kirill Kuvaldin <kirill.kuvaldin@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-cluster@redhat.com,
Andreas Dilger <adilger@sun.com>,
ocfs2-users@oss.oracle.com
Subject: Re: GFS2/OCFS2 scalability
Date: Mon, 23 Feb 2009 17:45:39 -0800 [thread overview]
Message-ID: <49A35143.9030804@oracle.com> (raw)
In-Reply-To: <2d42915c0902230420l291856a3r196e381e4e9f5c51@mail.gmail.com>
Kirill Kuvaldin wrote:
> What are the practical/theoretical limits for number of nodes for
> shared disk file systems like ocfs2/gfs2?
Theoretical limit is around 254 or so. Practical limit depends on
the hardware. Meaning, you cannot just add nodes. You have to
ensure the interconnect and the storage can handle the nodes. Also,
the more nodes you have, the more cpu/ram each node will have to dedicate
to the clustering overhead. Meaning, at some cluster size, dual core
nodes may not give you the best bang.
So with a GigE interconnect, 2/4G Fiber storage and dual core nodes,
32 to 64 nodes _may_ be the upper limit to the cluster size. A lot
depends on the workload... meaning hard numbers are not possible.
As far as clusters in use go, I have heard of 32 node ocfs2 clusters. Few.
More common is <= 20. 16 is quite common. mkfs.ocfs2 now defaults to 8...
meaning 8 is the very common.
> I did testing in a limited setup - a cluster of 4 xen domU of 128MB
> RAM with a shared block device mapped to a local LVM volume. My
> results could be wrong anyway ;)
You cannot really prototype a 100-1000 node cluster with 4 128MB
xen domUs.
prev parent reply other threads:[~2009-02-24 1:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 17:23 GFS2/OCFS2 scalability Kirill Kuvaldin
2009-02-20 19:50 ` Andreas Dilger
2009-02-21 1:59 ` Sunil Mushran
2009-02-23 12:20 ` Kirill Kuvaldin
2009-02-24 1:45 ` Sunil Mushran [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=49A35143.9030804@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=adilger@sun.com \
--cc=kirill.kuvaldin@gmail.com \
--cc=linux-cluster@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ocfs2-users@oss.oracle.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.