From owner-freebsd-fs@FreeBSD.ORG Thu Apr 25 18:44:02 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D0789A99 for ; Thu, 25 Apr 2013 18:44:02 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.208.146]) by mx1.freebsd.org (Postfix) with ESMTP id 70BA013A1 for ; Thu, 25 Apr 2013 18:44:02 +0000 (UTC) Received: from maia.hub.org (unknown [200.46.151.189]) by hub.org (Postfix) with ESMTP id 1B867B9808D; Thu, 25 Apr 2013 15:44:01 -0300 (ADT) Received: from hub.org ([200.46.208.146]) by maia.hub.org (mx1.hub.org [200.46.151.189]) (amavisd-maia, port 10024) with ESMTP id 80318-01; Thu, 25 Apr 2013 18:44:00 +0000 (UTC) Received: from [10.5.250.150] (remote.ilcs.sd63.bc.ca [142.31.148.2]) by hub.org (Postfix) with ESMTPA id DA63DB9808C; Thu, 25 Apr 2013 15:43:59 -0300 (ADT) Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: NFS Performance issue against NetApp From: "Marc G. Fournier" In-Reply-To: <972106612.1125159.1366850215231.JavaMail.root@erie.cs.uoguelph.ca> Date: Thu, 25 Apr 2013 11:43:58 -0700 Message-Id: <2F5E9262-E465-4837-9B35-6220970C185E@hub.org> References: <972106612.1125159.1366850215231.JavaMail.root@erie.cs.uoguelph.ca> To: Rick Macklem X-Mailer: Apple Mail (2.1503) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 18:44:02 -0000 On 2013-04-24, at 17:36 , Rick Macklem wrote: > If you explicitly set rsize=3DN,wsize=3DN on a mount, those sizes will = be > used unless they are greater than min(MAXBSIZE, server-max). MAXBSIZE = is > the limit for the client side buffer cache and server-max is whatever > the server says is its max, so the client never uses a value greater = than > that. Just got my new Intel card in, so starting to play with it =85 one thing = I didn't notice yesterday when I ran nfsstat -m: = nfsv3,tcp,resvport,soft,intr,cto,lockd,sec=3Dsys,acdirmin=3D3,acdirmax=3D6= 0,acregmin=3D5,acregmax=3D60,nametimeo=3D60,negnametimeo=3D60,rsize=3D6553= 6,wsize=3D65536,readdirsize=3D32768,readahead=3D1,wcommitsize=3D5175966,ti= meout=3D120,retrans=3D2 Earlier in this thread, it was recommended to change to 32k =85 and = Jeremy Chadwick thought it defaulted to 8k =85 My fstab entry right now is simply: 192.168.1.1:/vol/vm /vm nfs rw,intr,soft 0 = 0 so I'm not changing rsize/wsize anywhere =85 did those defaults get = raised recently and nobody noticed? or does it make sense to reduce = from 64k -> 32k to get better performance? Again, this is using a FreeBSD client to mount from a NetApp file server = ...=