linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lincoln Dale <ltd@cisco.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Phy Prabab <phyprabab@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux NFS vs NetApp
Date: Tue, 11 Jan 2005 22:38:35 +1100	[thread overview]
Message-ID: <5.1.0.14.2.20050111223726.044844e8@171.71.163.14> (raw)
In-Reply-To: <16867.41549.618.539945@cse.unsw.edu.au>

At 08:54 PM 11/01/2005, Neil Brown wrote:
>On Monday January 10, phyprabab@yahoo.com wrote:
> > Hello!
> >
> > I am trying to understand how NetApp can be so much
> > better at NFS servicing than my quad Opteron 250 SAN
> > attached machine.  So I need some help and some
> > pointers to understand how I can make my opteron
> > machine come on par (or within 70% NFS performance
> > range) as that of my NetApp R200.  I have run through
> > the NFS-how-to's and have heard "that is why they cost
> > so much more", but I really have to consider that
> > probably most of the ideas that are in the NetApp are
> > common knowldge (just not in my head).
> >
> > Can anyone shed some light on this?
>
>If you want to come anything close to comparable with a Netapp, get a
>few hundred Megabytes of NVRAM (e.g. www.umem.com), and configure it
>as an external journal for your filesystem (I know this can be done
>for ext3, I don't know about other filesystems).  Then make sure your
>filesystem journals all data, not just metadata (data=journal option
>to ext3).

NetApp's WAFL only journals metadata in NVRAM ...
(one of the primary reasons its called WAFL is that the data-write only 
happens once..).


cheers,

lincoln.

  reply	other threads:[~2005-01-11 11:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <message from Phy Prabab on Monday January 10>
2005-01-11  2:54 ` Linux NFS vs NetApp Phy Prabab
2005-01-11  3:58   ` Anton Blanchard
2005-01-11  7:42     ` Joel Jaeggli
2005-01-11  9:19       ` Valdis.Kletnieks
2005-01-11 10:01         ` Jakob Oestergaard
2005-01-11 14:43           ` J. Bruce Fields
2005-01-12 11:32             ` Jakob Oestergaard
2005-01-11 18:55           ` Valdis.Kletnieks
2005-01-11  9:54   ` Neil Brown
2005-01-11 11:38     ` Lincoln Dale [this message]
2005-01-11 22:02       ` Neil Brown
2005-01-11 23:36         ` Bernd Eckenfels
2005-01-12  0:41           ` Trond Myklebust
     [not found] <200501111711.50218.as@cohaesio.com>
2005-01-11 16:21 ` J. Bruce Fields
2005-01-11 17:53   ` Anders Saaby

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=5.1.0.14.2.20050111223726.044844e8@171.71.163.14 \
    --to=ltd@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=phyprabab@yahoo.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).