Path: utzoo!utgpu!watserv1!watmath!att!linac!uwm.edu!ux1.cso.uiuc.edu!news.iastate.edu!john From: john@iastate.edu (Hascall John Paul) Newsgroups: comp.protocols.nfs Subject: Re: how many nfsd's should I run? Message-ID: <1991Feb24.025821.11354@news.iastate.edu> Date: 24 Feb 91 02:58:21 GMT References: <28975@cs.yale.edu> Sender: news@news.iastate.edu (USENET News System) Organization: Iowa State University, Ames, IA Lines: 33 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? So far, we've seen four answers: -- 4 -- 8 -- (1 * n_disk_interfaces) + 1 -- (1 * n_disks_exported) + (1 * n_network_interfaces) Now, consider our situation (DEC 5000, 2 SCSI x 4 x 1GB, 1 net), that gives: -- 4 -- 8 -- 3 = (1 * 2) + 1 -- 10 = (1 * 8) + (1 * 1) We are running 20, which is almost assuredly too many. Does anyone have a solid answer for this question? Also does the number of clients to be served have any impact? Perhaps, a true answer can only be obtained empirically? Is there such a thing as a test-client which makes a series of nfs rpc calls to determine response time stats? I am sure many could benefit from such information [FAQ?]. Thanks, John Hascall -- John Hascall An ill-chosen word is the fool's messenger. Project Vincent Iowa State University Computation Center john@iastate.edu Ames, IA 50011 (515) 294-9551 Brought to you by Super Global Mega Corp .com