linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: Valdis.Kletnieks@vt.edu
Cc: Joel Jaeggli <joelja@darkwing.uoregon.edu>,
	Anton Blanchard <anton@samba.org>,
	Phy Prabab <phyprabab@yahoo.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux NFS vs NetApp
Date: Tue, 11 Jan 2005 11:01:10 +0100	[thread overview]
Message-ID: <20050111100109.GA347@unthought.net> (raw)
In-Reply-To: <200501110920.j0B9JwAL006980@turing-police.cc.vt.edu>

On Tue, Jan 11, 2005 at 04:19:57AM -0500, Valdis.Kletnieks@vt.edu wrote:
> On Mon, 10 Jan 2005 23:42:30 PST, Joel Jaeggli said:
> 
> > In actually using sfs97r1 published benchmarks to compare to hardware I 
> > was benchmarking (from emc, netapp and several roll-your own linux boxes) 
> > I found the published benchmark information alsmost entirely useless given 
> > that vendors tend to provide wildly silly hardware configurations. In the 
> > case of the openpower 720 (to use that for an example) the benchmarked 
> > machine has 70 15k rpm disks spread across 12 fibre channel controllers, 
> > 64GB of ram, 12GB of nvram and 7 network interfaces...
> 
> If you threw that much hardware at a Linux system, 

... theory ... or have you actually tried?

> and then tuned it so that it
> didn't really care about userspace performance (oh.. say.. by giving the knfsd
> thread a RT priority ;), and tuned things like the filesystem, the slab
> allocator and the networking stack to NFS requirements, it probably would be
> screaming fast too.. ;)

You'd need to run a 2.4 kernel.

Current problems with 2.6:
1 ext3 causes kjournald oops on load
2 xfs has bad NFS/SMP/dcache interactions (you end up with undeletable
  directories)
3 knfsd will give you stale handles (can be worked around by stat'ing
  all your directories constantly on the server side)

The SGI XFS kernel from CVS actually almost solved (2) above, but not
entirely - I was going to report on that again to LKML. The other
problems are still, as far as I know, unsolved.

Not trying to flame anyone here, just trying to be realistic  ;)

-- 

 / jakob


  reply	other threads:[~2005-01-11 10:01 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 [this message]
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
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=20050111100109.GA347@unthought.net \
    --to=jakob@unthought.net \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=anton@samba.org \
    --cc=joelja@darkwing.uoregon.edu \
    --cc=linux-kernel@vger.kernel.org \
    --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).