All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hugh Caley <hcaley@plasmabat.com>
To: nfs@lists.sourceforge.net
Subject: Performance Difference Between Linux NFS Server and Netapp
Date: Mon, 11 Jul 2005 15:55:53 -0700	[thread overview]
Message-ID: <42D2F8F9.4010304@plasmabat.com> (raw)

I've been doing a little limited benchmarking of NFS performance, and
doing a comparison between Linux NFS servers and a Netapp.  All tests
done over gigabit, clients are Linux (i386 and Opteron), OS is Fedora
Core 2,
kernel is 2.6.10-1.771_FC2smp, filesystem is Reiser.  I basically copy a
205
megabyte file to the server three times and average the results.  Sure,
limited,
but it seems to have real world relevance here.

The difference in performance is kind of startling.  I had originally
put the Linux-based servers (with a Nexsan Atabeast backend) in as a
replacement for an older EMC Celerra and a few older Suns.  On both the
Suns and Celerra I would see single-client performance topping out at
between 120 and 150 megabits per second.

The Linux setup (Supermicro Dual 2.6 Ghz Xeons with 4 gigabytes of RAM,
recently boosted to 8 gigabytes of RAM) regularly returns about 300
megabits per second.  Given the difference in price between the Linux
boxes and the Celerra, everyone's pretty happy ;)

However, recently I've been trying the same testing between Linux
clients and a Netapp, and can achieve between 500 and 600 megabits per
second!  Darned impressive.

I realize that the disk subsystem of the Netapp is going to stomp on my
Atabeast, but neither 300 nor 600 megabits is anywhere near the speed I
can get if I run the same test locally on the Linux server boxes, which
can regularly top 2000 megabits per second, so I really don't think that
the differences in disk architecture should make this much difference.

I guess my question is, are my Linux NFS servers seriously
underperforming?  Could I expect to achieve better?  I realize that my
"benchmark" is pretty limited, but the difference is pretty big.  Since
the same client
on all the Linux boxen gets these results, I'm guessing that the client end
has little to do with it.

How does Netapp do it?  Don't suppose they'd tell me ...

Hugh

--
Hugh Caley | Unix Systems Administrator | CIS
AFFYMETRIX INC. | 6550 Vallejo St. Ste 100 | Emeryville, CA 94608
Tel: 510-428-8537 | Hugh_Caley@affymetrix.com

-- 
"Brain-eating mutants are bad for business" - Battle Angel
Batmensch <hcaley@plasmabat.com>



-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2005-07-11 22:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11 22:55 Hugh Caley [this message]
2005-07-12 16:24 ` Performance Difference Between Linux NFS Server and Netapp Roger Heflin
2005-07-12 16:34   ` Joshua Baker-LePain
2005-07-12 18:19     ` Hugh Caley
2005-07-14 11:25 ` Sten Spans
2005-07-14 18:21   ` Hugh Caley
2005-07-14 19:50     ` Chris Penney
  -- strict thread matches above, loose matches on Subject: below --
2005-07-14 20:41 Hugh Caley

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=42D2F8F9.4010304@plasmabat.com \
    --to=hcaley@plasmabat.com \
    --cc=nfs@lists.sourceforge.net \
    /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.