linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joel Jaeggli <joelja@darkwing.uoregon.edu>
To: Anton Blanchard <anton@samba.org>
Cc: Phy Prabab <phyprabab@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux NFS vs NetApp
Date: Mon, 10 Jan 2005 23:42:30 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0501102321490.25796@twin.uoregon.edu> (raw)
In-Reply-To: <20050111035810.GG14239@krispykreme.ozlabs.ibm.com>

On Tue, 11 Jan 2005, Anton Blanchard wrote:

>
>> 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?

you have to quantify what sort of hardware you're benchmarking in either 
case and how its configured before you can reasonably conclude to much... 
I spent quite a bit of time benchmarking filers and linux configurations 
recently and while I can say with some certainty that while netapp makes 
some very fast and well balanced filers they don't by any means have a 
lock on building a high-performance nfs box.

> Definitely sounds like something is wrong. You can do your own
> comparisons of Linux 2.6 vs Netapp here (the OpenPower 720 is a ppc64
> Linux box):
>
> http://www.spec.org/sfs97r1/results/sfs97r1.html

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...

> Anton
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

-- 
-------------------------------------------------------------------------- 
Joel Jaeggli  	       Unix Consulting 	       joelja@darkwing.uoregon.edu 
GPG Key Fingerprint:     5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2


  reply	other threads:[~2005-01-11  7:44 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 [this message]
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
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=Pine.LNX.4.61.0501102321490.25796@twin.uoregon.edu \
    --to=joelja@darkwing.uoregon.edu \
    --cc=anton@samba.org \
    --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).