From owner-freebsd-hackers Mon Aug 9 1:50: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 37D28151E1 for ; Mon, 9 Aug 1999 01:49:45 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id EAA06476; Mon, 9 Aug 1999 04:50:53 -0400 (EDT) Date: Mon, 9 Aug 1999 04:50:51 -0400 (EDT) From: Alfred Perlstein To: Doug Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Fix/tuning to improve slow NFS writes? In-Reply-To: <37AE8730.886D4E72@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Aug 1999, Doug wrote: > 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? ? You need to run 'nfsd' on the servers, not nfsiod. nfsd - run on server nfsiod - run on client nfsd takes the same -n arg for the number to start. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message