Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!emory!gatech!mcnc!uvaarpa!murdoch!astsun7.astro.Virginia.EDU!gl8f From: gl8f@astsun7.astro.Virginia.EDU (Greg Lindahl) Newsgroups: comp.protocols.nfs Subject: Re: how many nfsd's should I run? Message-ID: <1991Feb22.012532.26075@murdoch.acc.Virginia.EDU> Date: 22 Feb 91 01:25:32 GMT References: <28975@cs.yale.edu> Sender: usenet@murdoch.acc.Virginia.EDU Organization: Department of Astronomy, University of Virginia Lines: 20 In article <28975@cs.yale.edu> anselmo-ed@CS.YALE.EDU (Ed Anselmo) writes: >Is there a magic formula for determining how man nfsd's to run? I was once told that the mystical figure was "one per network interface and one per disk with exported filesystems." >What happens when you run too many nfsd's? Too few? If you have too many processes competing for the limited slots in the hardware context cache, your machine will roll over and die. You can look up this number in you hardware manuals somewhere. For low-end sun4's the number is 8. I run 4 nfsd's on such machines. The same problem can bite you with too many biods. Another good thing to check is NFS timeouts... nfsstat(8C) will tell you if the server is responding sufficiently quickly. I raised my timeout until I saw zero timeouts. Disclaimer: I'm not an expert, but I once asked for help on this very topic here and nobody answered ;-) Brought to you by Super Global Mega Corp .com