From: James Pearson <james-p@moving-picture.com>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: render farm NFS server is having hard time staying up.
Date: Tue, 19 Oct 2004 17:59:16 +0100 [thread overview]
Message-ID: <417547E4.8070905@moving-picture.com> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C61130435E9B5@lavender-fe.eng.netapp.com>
Lever, Charles wrote:
>>24 nfsd's fire off at startup.
>
>
> if you try more than 24, does that help or hurt the situation?
>
>
>>I have added this as part of the system startup:
>>echo 262144 > /proc/sys/net/core/rmem_default
>>echo 262144 > /proc/sys/net/core/rmem_max
>>/etc/init.d/nfs start
>>echo 65536 > /proc/sys/net/core/rmem_default
>>echo 65536 > /proc/sys/net/core/rmem_max
>
>
> i don't understand why you reset these values after you've started nfs.
> 262144 should be safe to use all the time, and for both rmem and wmem.
Probably because it says so in the NFS-HOWTO ...
see:
http://nfs.sourceforge.net/nfs-howto/performance.html#MEMLIMITS
James Pearson
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-10-19 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 15:44 render farm NFS server is having hard time staying up Lever, Charles
2004-10-19 16:59 ` James Pearson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-19 15:35 Greg Whynott
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=417547E4.8070905@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=Charles.Lever@netapp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox