All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Penney <cpenney@gmail.com>
To: nfs@lists.sourceforge.net
Subject: Re: Performance Difference Between Linux NFS Server and Netapp
Date: Thu, 14 Jul 2005 15:50:09 -0400	[thread overview]
Message-ID: <111aefd050714125064cb549e@mail.gmail.com> (raw)
In-Reply-To: <42D6AD28.3030204@plasmabat.com>

[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]

On 7/14/05, Hugh Caley <hcaley@plasmabat.com> wrote: 
> 
> A valid point, of course, but I don't think I'm actually expecting a
> single NFSd to act like an expensive Netapp. I do think that wondering
> why the Netapp is twice as fast for a sequential write is a valid
> question, even if the OS and NFS server subsystem are free. I was kind
> of hoping someone would just say "you're getting what you should expect
> to get" or "wow, that's slow, try this and this and this".

 You referenced that you were getting 300 megabits (or 37MB/s). I have 
several SLES 9 nfs servers (using self compiled 2.6.11.5
<http://2.6.11.5>kernel) running on IBM x345 hardware (dual cpu pentum
4, 2gb ram, dual
qlogic hbas) connected to a single LSI storage array that presents four luns 
(two from controller A and two from B). Each lun is 1TB and made from 
hardware raid 8+1. Luns are merged together using device mapper.
 It's not uncommon with my setup to get a sustained write speed of 75MB/s on 
one of our SLES 9 compute systems (AMD Opterons) when doing a sequential 
write of an 8GB file. With two systems writing at the same time I get 
aggregate bandwidth better than 75MB/s (can't recall what it is).
 I use tcp/nfs3 and for write testing I use 'iozone -c -e -s 8192m -i 0'. I 
use 128 nfsds, export with 'rw,sync,no_subtree_check,no_root_squash' and add 
the following to sysctl.conf:
 net.core.rmem_default = 262144
net.core.wmem_default = 262144
net.core.rmem_max = 8388608
net.core.wmem_max = 8388608
net.ipv4.tcp_rmem = 4096 87380 8388608
net.ipv4.tcp_wmem = 4096 65536 8388608
net.ipv4.tcp_mem = 8388608 8388608 8388608
 On nfs clients (Sun, Linux, IRIX) I use the mount options: 
nosuid,rw,bg,hard,intr,vers=3,proto=tcp,rsize=32768,wsize=32768. On AIX I 
use the same options, but also add the critical 'combehind' (without it 
writes of large files [ie. close to the size of physical mem] is just 
horrid). 
  Chris

[-- Attachment #2: Type: text/html, Size: 2494 bytes --]

  reply	other threads:[~2005-07-14 19:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11 22:55 Performance Difference Between Linux NFS Server and Netapp Hugh Caley
2005-07-12 16:24 ` 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 [this message]
  -- 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=111aefd050714125064cb549e@mail.gmail.com \
    --to=cpenney@gmail.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=penney@msu.edu \
    /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.