From owner-freebsd-hackers Mon Aug 9 8:31:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 688F0150B1 for ; Mon, 9 Aug 1999 08:31:13 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA62751; Mon, 9 Aug 1999 08:27:55 -0700 (PDT) (envelope-from dillon) Date: Mon, 9 Aug 1999 08:27:55 -0700 (PDT) From: Matthew Dillon Message-Id: <199908091527.IAA62751@apollo.backplane.com> To: Doug Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Fix/tuning to improve slow NFS writes? References: <37AE266D.D71D89EF@gorean.org> <199908090706.AAA59059@apollo.backplane.com> <37AE8730.886D4E72@gorean.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : I should have mentioned, I have 20 nfsiod's running. I started so many :initially to help in the stress testing I was doing, but I left them :running because the servers are handling from 2-4 requests per second and :we have lots of ram in the boxes. Is there a way to figure out how many are :getting used concurrently, or is too many not a problem? : :Thanks, : :Doug You can look at their cpu utilization with ps. You should see high cpu use on a couple of them and then tapering off. The system allocates nfsiods in order depending on the number of outstanding asynchronous requests. If the web server is not bound by write bandwidth, it could be getting bound up in NFS stat calls. I think what you need to do at this point is run ktrace on some of the web server processes to see where the performance bottlenecks are. Let ktrace collect statistics for a while and then make sure to turn it off with 'ktrace -C', and then use 'kdump -R | less' to see the results. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message