On Fri, Oct 31, 2008 at 5:47 PM, Miles O'Neal <[log in to unmask]> wrote:

useful info deleted for focus.

> So, we have two (possibly) problems.
>
> 1) Are the stats wrong, or is the problem not really
>   in the number of threads?  This is a fast, dual,
>   quadcore SuperMicro server, so I'm not worried
>   that it can handle the load; we have much slower
>   systems handling 100 threads without a hiccup
>   (the nature of the projects means this newer
>   system will get a lot more traffic).
>
>   The NIC doesn't seem to be swamped.
>
>   Is there a kernel param I need to tweak for
>   more open sockets or something?
>

actually I think you need to look at the various nfs kernel proc/sys
items first before bumping up the number of threads. You could be
saturating various memory handlers and such and then you are just
exasperating the problem with more threads and such. The process may
be running out of open files or other items.

> 2) If I do need more daemons, how do I determine
>   how much memory I need?  What is the limit on
>   the number of daemons?

Well the big issue may not be memory at that point but 32bit versus
64bit. The box might run out of possible allocations at 4GB of ram as
that is as much one process can map to. I am guessing that each nfsd
is allocating potential memory it can use for readahead and is running
out of what it can set-aside for a buffer.



-- 
Stephen J Smoogen. -- BSD/GNU/Linux
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"