On Tue, Apr 15, 2008 at 07:42:45AM +0200, Carsten Aulbert wrote: > By the ways, discussing this issue with my colleague cluster admins, the > question popped up, if there is a guideline/rule of thump of how many > nfsd one should run - or asking the other way round, how to arrive at a > good compromise. > > Our server boxes are pretty big (8 cores, 16 GB memory, 16 disk > Areca1261 RAID6), so the resources used by the nfsd are not much of an > issue - I even tested with 1024 nfsd idling around. AT some point > increasing the number does not make much sense because I cannot get the > data out fast enough or the seeks will likely "kill" the box^Wperformance. > > Any thoughts on that? The only advice I know of is to check the "th" line in /proc/net/rpc/nfsd and adjust the number of threads until you can verify that they're rarely all in use; see http://nfs.sourceforge.net/nfs-howto/ar01s05.html#nfsd_daemon_instances --b. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ NFS maillist - NFS@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@xxxxxxxxxxxxxxxxxxxxx is being discontinued. Please subscribe to linux-nfs@xxxxxxxxxxxxxxx instead. http://vger.kernel.org/vger-lists.html#linux-nfs -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
