Linux filesystem development
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@sun.com>
To: Kirill Kuvaldin <kirill.kuvaldin@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, ocfs2-users@oss.oracle.com,
	linux-cluster@redhat.com
Subject: Re: GFS2/OCFS2 scalability
Date: Fri, 20 Feb 2009 12:50:30 -0700	[thread overview]
Message-ID: <20090220195030.GE3199@webber.adilger.int> (raw)
In-Reply-To: <2d42915c0902200923u6c539fbdh3ec1a147b4daa396@mail.gmail.com>

On Feb 20, 2009  20:23 +0300, Kirill Kuvaldin wrote:
> I'm evaluating different cluster file systems that can work with large
> clustered environment, e.g. hundreds of nodes connected to a SAN over
> FC.
> 
> 
>  So far I looked at OCFS2 and GFS2, they both worked nearly the same
> in terms of performance, but since I ran my tests in a local limited
> environment with 4 nodes in a cluster, the results can't be
> extrapolated to 100 nodes.
> 
> Is there any reading on comparison of OCFS2/GFS2 scalability? And
> could these FS scale up to environment of that size (100-1000 nodes,
> 10-100Tb storage) or should I look to proprietary solutions like IBM
> GPFS, HP Polyserve, etc... ?

I'm fairly biased, but I think you should look at Lustre - it is currently
running on 15 of the 20 fastest systems in the world, and 40% of the top 200.
No problems with scalability at all - the ORNL Jaguar system has 37000+
nodes, 10PB of storage, and has exceeded 150GB/s peak read/write speed.

Lustre is GPL and freely available: http://www.lustre.org/

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.


  reply	other threads:[~2009-02-20 19:51 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 [this message]
2009-02-21  1:59   ` Sunil Mushran
2009-02-23 12:20     ` Kirill Kuvaldin
2009-02-24  1:45       ` Sunil Mushran

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=20090220195030.GE3199@webber.adilger.int \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox