From owner-freebsd-questions Sun Feb 9 16:18:47 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BCF737B401 for ; Sun, 9 Feb 2003 16:18:45 -0800 (PST) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id E299E43F85 for ; Sun, 9 Feb 2003 16:18:44 -0800 (PST) (envelope-from tillman@seekingfire.com) Received: from blues.seekingfire.prv (blues.seekingfire.prv [192.168.23.211]) by mail.seekingfire.com (Postfix) with ESMTP id 4AEB445 for ; Sun, 9 Feb 2003 18:18:44 -0600 (CST) Received: (from tillman@localhost) by blues.seekingfire.prv (8.11.6/8.11.6) id h1A0KSW12911 for freebsd-questions@FreeBSD.ORG; Sun, 9 Feb 2003 18:20:28 -0600 Date: Sun, 9 Feb 2003 18:20:28 -0600 From: Tillman To: freebsd-questions@FreeBSD.ORG Subject: Re: speeding up NFS Message-ID: <20030209182028.C32740@seekingfire.com> References: <200302091717.42138.ajacoutot@lphp.org> <20030209192839.GH5356@dan.emsphone.com> <20030209174109.B32740@seekingfire.com> <3E46E7BE.9080308@potentialtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3E46E7BE.9080308@potentialtech.com>; from wmoran@potentialtech.com on Sun, Feb 09, 2003 at 06:43:58PM -0500 X-Urban-Legend: There is lots of hidden information in headers Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Feb 09, 2003 at 06:43:58PM -0500, Bill Moran wrote: > Tillman wrote: > > I'm getting about > > 8.5-9 Megabytes/s on NFS reads from a Linux 2.4 client (on a 100Mbit > > switched LAN) with it set to 0, as measured by Bonnie++. This is fairly > > close to the 12MB/s fast ethernet theoretical maximum, so I'm happy with > > performance. > > What did you change to get it running that fast? Many many bonnie++ runs and careful charting of the results :-) Client side (Linux 2.4): Mount with mountvers=3,hard,intr,nolock,udp,wsize=8192,rsize=8192 Note that w/r sizes above 8k require a small kernel patch to Linux - and I found that it's typically a tad /slower/ than 8k in any case. Not worth it according to the benchmarking I did. In general, version 3 was much better performing than version 2 (where async vs. sync was more of an issue). On the server side, ensure that you have enough nfsd's to handle all requests by keeping an eye on the `ps` output. When one or more of the nfsd's have no CPU time, then you've just started to cross the line into too many (which is about right). Also, ensure that you're not disk I/O limited on the server side. I'm currently using a couple of vinum arrays where I'm reading at about 30MB/s and the random seeks are high (about 530/sec). This puts any blame for slowness on the network (and NFS), which simplified tuning. I'd welcome benchmarks to the contrary, I could always use more NFS performance ;-) -T -- Yield to temptation; it may not pass your way again. Robert Heinlein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message