From: Chris Worley <cworley@lnxi.com>
To: didier@ece.gatech.edu
Cc: nfs@lists.sourceforge.net
Subject: RE: Pb of optimization for a Cluster under Gigabit
Date: 07 Apr 2004 15:31:40 -0600 [thread overview]
Message-ID: <1081373500.2556.16643.camel@localhost> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C61130435DEAA@lavender-fe.eng.netapp.com>
On Wed, 2004-04-07 at 14:58, Lever, Charles wrote:
> >
> > That definitely helped. Now the NFS options passed
> > via automount to the client are:
> >
> > rw,nfsvers=3,udp,hard,intr,rsize=8192,wsize=8192
> >
> > However, the load of the nfs server still goes up to 3.5
Is that option string coming from /proc/mounts, or actually what you're
using? If it's coming from /proc/mounts, then not all options are
echoed... and, one thing to definitely get the load level up on the
server is using the "noac" option on the clients.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-04-07 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 20:58 Pb of optimization for a Cluster under Gigabit Lever, Charles
2004-04-07 21:31 ` Chris Worley [this message]
2004-04-08 2:17 ` Didier CONTIS
-- strict thread matches above, loose matches on Subject: below --
2004-04-07 4:39 Lever, Charles
2004-04-07 20:46 ` Didier CONTIS
2004-04-07 3:22 Didier CONTIS
2004-04-07 5:28 ` Greg Banks
2004-04-07 11:40 ` Bogdan Costescu
2004-04-07 20:38 ` Didier CONTIS
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=1081373500.2556.16643.camel@localhost \
--to=cworley@lnxi.com \
--cc=didier@ece.gatech.edu \
--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