From owner-freebsd-hackers Mon Aug 9 0:49:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 2421514E84 for ; Mon, 9 Aug 1999 00:49:32 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id AAA36356; Mon, 9 Aug 1999 00:45:51 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37AE8730.886D4E72@gorean.org> Date: Mon, 09 Aug 1999 00:45:52 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0730 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Fix/tuning to improve slow NFS writes? References: <37AE266D.D71D89EF@gorean.org> <199908090706.AAA59059@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > : So, the big question is whether there is anything we can tune to speed up > :the writes. The freebsd machines are NFS clients to the sun servers doing > :most of the web processing. Overall performance on the reads seems to be > :best with nfs v3 over udp, which is what I'm using now. All of the web > :server directories are soft mounted directly, with no amd currently in use. > : > :thanks, > : > :Doug > > Well, NFS buffers are usually sent over the network the moment they > are full. If you are not running any nfsiod's 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message