From: Matt Schillinger <mschilli@vss.fsi.com>
To: nfs@lists.sourceforge.net
Subject: NFS Tuning
Date: 15 May 2003 06:24:45 -0500 [thread overview]
Message-ID: <1052997886.12158.10.camel@mosix> (raw)
For NFS Version 3, is there a formula to help administrators tune NFSD
to their environment?
I'm looking at thread count, and obviously see the advantages that
adding threads to a server that is experiencing large number of thread
overutilization, but I am wondering if there is a way to best calculate
the threads needed.
Such as:
CPU Speed:
RAM:
Total Bandwidth of Serving Network Interfaces, and How many network
interfaces served:
Number of Clients: (Would OS of clients affect - are some 'more
efficient consumers than others?)
Equals: How many threads this machine can handle or should be using.
Also, another tuning item i found was for Memory limits for the input
queue. It recommends 256K for a standard install, as opposed to the
default 64K.
Standard setup has 8 threads, so 256K gives each thread 32K input queue.
For 16 threads, does the calculation still hold true? (512K input queue=
32K/thread) What are the signs that can allude to input queue problems?
I'm just trying to tune my servers in a less than trial and error
method.
Thanks for your help,
--
Matt Schillinger
mschilli@vss.fsi.com
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2003-05-15 11:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1052997886.12158.10.camel@mosix \
--to=mschilli@vss.fsi.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