From owner-freebsd-current Sat Aug 21 17:30:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt011n65.san.rr.com (dt010nb9.san.rr.com [204.210.12.185]) by hub.freebsd.org (Postfix) with ESMTP id DA1F514E3E; Sat, 21 Aug 1999 17:30:55 -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 RAA83650; Sat, 21 Aug 1999 17:28:06 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37BF4420.452C5076@gorean.org> Date: Sat, 21 Aug 1999 17:28:16 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0815 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: "John S. Dyson" , Alfred Perlstein , Eivind Eklund , Peter Wemm , current@FreeBSD.ORG Subject: Re: NFS HEADS UP (was Re: cvs commit: src/sys/nfs nfsm_subs.h xdr_subs.h) References: <199908211156.GAA20231@dyson.iquest.net.> <199908211649.JAA73759@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > Does anyone know why our NFS clients are sending a separate RPC for each > 8K buffer? If the dirty space is contiguous across a number of buffers > we should be able to send a *SINGLE* commit rpc to the server. That would > greatly reduce system overhead on both the client and server when writing > a large file over NFS. This would seem to be an almost free optimization > that would mesh extremely well with the nfsrv_commit optimizations I'm > making right now. > > At the moment I can saturate a 100BaseTX with NFS writes and get > 10 MBytes/sec to the platter on the server, but the cpu required on both > the client and server to do that is well over 60% of a Pentium III-450. I'd like to put in a vote to get these NFS write optimizations in the pipe ASAP. The last hurdle (seemingly) on my big project at work that I've been bugging so many of you about is the fact that FreeBSD NFS client writing to Sun NFS server is just DOG slow. I did some pretty extensive testing on this and couldn't come up with any client option twidding that made any difference, except increasing wsize to 16k, which got me about 10%, but it was still very slow. This is on a -current system from around the tenth of August. Matt, thanks for all your hard work on this, and believe me when I say it couldn't come at a better time. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message