From owner-freebsd-stable@FreeBSD.ORG Mon Apr 18 21:05:59 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8170316A4CE for ; Mon, 18 Apr 2005 21:05:59 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A93143D3F for ; Mon, 18 Apr 2005 21:05:58 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual.digiware.nl [212.61.27.71]) by freebee.digiware.nl (8.13.1/8.13.1) with ESMTP id j3IL5u0r056306; Mon, 18 Apr 2005 23:05:56 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <42642135.3040004@withagen.nl> Date: Mon, 18 Apr 2005 23:05:57 +0200 From: Willem Jan Withagen User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Claus Guttesen References: <6eb82e05041500274172afd3@mail.gmail.com> <20050416122222.GA12385@totem.fix.no> <6eb82e0504160536572e068c@mail.gmail.com> <20050416183755.GB61170@xor.obsecurity.org> <4262CFBF.4090709@withagen.nl> <4264104B.2030600@withagen.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: stable@freebsd.org cc: Kris Kennaway Subject: Re: NFS defaults for read/write blocksize....(Was: Re: 5.4/amd64 console hang) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2005 21:05:59 -0000 Claus Guttesen wrote: >> >>How did you come to this conclusion? What kind of workload? > > > To make a short story long ;-) > > Last year just after christmas I got a new storage system and had an > opportunity to replace our Linux-nfs-server with FreeBSD. I searched > the archives for nfs-related tuning-information, and found some links > suggesting the usage of tcp rather than udp and adjusting the > r/w-size. So I nfs-mounted some clients and started to copy back and > forth. The december release of the (back then) current had some > "server not responding" messages, but they appeared less with > r/w-sizes of 32768. The copying itself was faster as well. > > So I upgraded (two or three times) until I had the Feb. 18'th 2004 > current and the "server not responding" almost vanished. Some weeks > after that the server went into production and have been rock-stable! > It went down once but that was only due to a poweroutage that lasted a > few hours, longest uptime was 117 days before I took it down for > servermaintenance. > > The files are at most some MB in size (images) and some KB (thumbnails). > > >>This is in line with what the graphs suggest: >> Use Laaarrrrrggggeee sizes. > > > And use tcp as well. I would conclude use UDP if they are on the same net/switch. Block reading is more or less equal for both. Block writing is slightly better for UDP, both there is a strange dip for 4Mb filesize. Which was very repeatable, but I can not explain. If you'd have a lot of rewriting, I'd say UDP as well, but 8K szie would be better. --WjW