my question concerned the number of nfs server threads to
use in Solaris 2.X. i asked what value to use for the
nservers parameter of nfsd, and how to measure the impact
or improvement in system performance.
the criteria given to calculate the value comes from comes
from adrian cockcroft's book sun performance and tuning, 1995,
p.89. the suggested value to use comes from the highest number
calculated from 3 rules:
1. 2 threads per active client process
2. 32 threads on a SPARCclassic server, 64 per SuperSPARC processor
3. 16 per Ethernet, 160 per FDDI
i received the following answer from hal stern, hal.stern@sunworld.com,
that i'd like to pass on:
> in solaris, there's really no harm in having too many threads.
> the limit is a high water mark, not a fixed resource allocation.
>
> figure on 2000 for a big server, 1000 for a mid-range, 500 for
> a low-end server and 250 for a desktop (ss2/ss10 flavor).
>
> you'll see some improvement in performance by adding more threads
> in terms of better response time, more throughput (more nfsops/sec
> on the server), etc.
>
> --hal
my thanks to Aindi Paton,apaton@wtl1.demon.co.uk, who provided this:
>
>I don't know about benchmarks but a sign of not having enough nfsds is
># netstat -s | fgrep udpInOverflows (Solaris 2)
>
> udpInCksumErrs = 0 udpInOverflows = 0
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> If this is not zero try
> adding extra threads/nfsds
>
thanks very much.
cathy
***************************************************************************
Cathy L. Hargrave phone: (214) 466-7599
SGS-Thomson Microelectronics, Inc. fax: (214) 466-7279
1310 Electronics Drive - MS 600 e-mail: cathy@stm.com
Carrollton, TX 75006
***************************************************************************
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:09 CDT