This may not help you but... NFS connection speed will be greatly hampered
if the NFS serving computer does not know the name of the client making a
request. If you are not using a DNS on your LAN, if your IP address are
assigned and static, make sure that your NFS server has an entry in it's
/etc/hosts file for each client that wants to make a connection. My
/etc/hosts file is this.
192.168.0.2 Jason.Ept Jason
192.168.0.5 sasquatch.EPT sasquatch
192.168.0.80 StoVoKor.Ept StoVoKor
192.168.0.86 OlympusMons.Ept OlympusMons
192.168.0.89 UtopiaPlanitia.Ept UtopiaPlanitia
192.168.0.200 Brother.lpd Brother
192.168.0.250 KVort.Ept KVort
192.168.0.254 Gateway.gwr Gateway
If connection speed is not the problem but transfer speed it I would look
at hardware as the problem.
> I had just configured a NFS server on eDesktop 2.4 and tried a NFS client
> on Redhat 6.1 to mount it. But I found that the speed was slow. Slow
> means for 2 cases:
> 1. The first time to access the directory, there were several seconds
> of delay.
> 2. During vi of a file, the response was slow
> I checked with ps -ef on the NFS server and found:
> root 632 1 0 17:09 ? 00:00:00 nfsd 4
> root 1013 632 0 17:14 ? 00:00:00 nfsd 4
> root 1014 632 0 17:14 ? 00:00:00 nfsd 4
> root 1015 632 0 17:14 ? 00:00:00 nfsd 4
> Is it the only reason is there're too few daemons are running ?
> How can I increase it ? How to calculate how much is the best
> (opt for speed) ?
> Thanks, rgds