Linux NFS development
 help / color / mirror / Atom feed
From: "Iain Irwin-Powell" <iain@cinesite.co.uk>
To: <nfs@lists.sourceforge.net>
Subject: NFS Performance Between SGI Servers and Linux Clients
Date: Thu, 22 May 2003 17:32:22 +0100	[thread overview]
Message-ID: <008601c3207f$b8bfd160$0b00430a@granger> (raw)


Does anyone have any ideas about this?

We have been experiencing a number of issues regarding NFS serving on
SGI IRIX (6.5.19) servers which now appear to point back to Linux NFS
clients.

The server is an Origin 2000, quad processors, 1.5GB memory, serving
over Gigabit. This can be reproduced on connections whether or not they
are using jumbo frames. The disks that are served are hardware RAID3
capable of around 80-90MB/s (tested and optimised not theoretical). 

Under certain circumstances will get a load average of 8 (or how ever
many nfsd's are running). The server itself is not that busy. Most of
the nfsd's show as sleeping but they are obviously waiting for
something.

Further investigation revealed that this situation arises when a Linux
client opens many files in quick succession (doing
open-read-close,open-read-close). We tend to use files in the range
3MB-13MB in size generally.

If we do the same test on an SGI client there is very little impact on
the load average.

We can recreate this by doing (on the client);

find . -type -f -print -exec grep jsdhgkhjfdk {} \;

The same effect appears to happen on Linux servers as well. A single
Linux client doing this will make the load average creep up towards 2.5.

Linux Version 2.4.20
nfs-utils-1.0.1-1
exports are exported with -32bitclients

Looking a bit deeper in a packet trace when the grep is running, Linux
seems to issue 16 read requests (16KB) at a time whilst an SGI will only
issue between 2 and 4. May or may not be relevant.

This information has also been passed back to SGI who are looking at it.

Packet traces and more detail is available if anyone wants them.

Any ideas or suggestions would be welcome.

******************************************************************
Iain Irwin-Powell (AKA Iain Powell)
Senior Systems Administrator
Cinesite Europe Limited
9 Carlisle Street
London
W1D 3BP
 
T: +442079734000
DDI: +442079734053
*******************************************************************
It's not broken, it just doesn't work the way you expected.
*******************************************************************




-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2003-05-22 16:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 16:32 Iain Irwin-Powell [this message]
2003-05-22 21:12 ` NFS Performance Between SGI Servers and Linux Clients Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2003-05-22 22:07 Lever, Charles
2003-05-22 22:23 ` Trond Myklebust
2003-05-23 12:11   ` Danny Smith
2003-05-28  9:02     ` Iain Irwin-Powell
2003-05-23 11:14 Kiernan, Michael
2003-05-23 12:09 ` Danny Smith

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='008601c3207f$b8bfd160$0b00430a@granger' \
    --to=iain@cinesite.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox