On Tue, Nov 05, 2002 at 06:44:47PM +0100, Lasse Laursen wrote:
How is the optimum number of nfsd processes determined on the server? On
our current setup we have 4 nfs daemons running serving 3 clients
(webservers)
Is the number of daemons to start determined by the number of clients or
the
On Wed, 2002-11-06 at 19:52, BigBrother wrote:
Although the man page says this, I *think* that the communication is done
like this
CLIENT = NFSIOD(CLIENT) = NFSIOD (SERVER) = NFSD
which menas that NFSIOD 'speak' with each other and then they pass the
requests to NFS.
Of course if u
I recently did some research into NFS performance tuning and came across
the suggestion in an article on onlamp.com by Michael Lucas, that 32768
is a good value for the read and write buffers. His suggestion is these
flags:
tcp,intr,nfsv3,-r=32768,-w=32768
I used these options (I found tcp was
Howdy!
I have done some simulations with NFS servers - Intel SCB2 (4G RAM)
serving files from 500G RAID devices. I created a treed directory structure
with 300G of 32k files that approximates our homedirectory structure.
I had about 6 diskless front ends (tyan 2518 with
Hi,
According to my experience UDP is much preffered for NFS transport
protocols. Also try to have the NFSIOD daemon being executed on every
machine by putting in the /etc/rc.conf
nfs_client_enable=YES
nfs_client_flags=-n 10
[u may put more than 10 instances if u suspect that more than
According to my experience UDP is much preffered for NFS transport
protocols. Also try to have the NFSIOD daemon being executed on every
machine by putting in the /etc/rc.conf
nfs_client_enable=YES
nfs_client_flags=-n 10
[u may put more than 10 instances if u suspect that more than 10
Hi,
Thanks for your reply. I have some additional questions:
Well the only rule for selecting the number of nfsiods and nfsd is the
maximum number of threads that are going to request an NFS operation on
the server. For example assume that your web server has a typical number
of httpd
I recently did some research into NFS performance tuning and came across
the suggestion in an article on onlamp.com by Michael Lucas, that 32768
is a good value for the read and write buffers. His suggestion is these
flags:
tcp,intr,nfsv3,-r=32768,-w=32768
I used these options (I found tcp was
