From owner-freebsd-hackers@FreeBSD.ORG  Sat Feb 19 13:36:08 2005
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4794616A4CE; Sat, 19 Feb 2005 13:36:08 +0000 (GMT)
Received: from sollube.sarenet.es (sollube.sarenet.es [192.148.167.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id BF1F143D41; Sat, 19 Feb 2005 13:36:07 +0000 (GMT)
	(envelope-from borjamar@sarenet.es)
Received: from [127.0.0.1] (borja.sarenet.es [192.148.167.77])
	by sollube.sarenet.es (Postfix) with ESMTP id 633B4BB6;
	Sat, 19 Feb 2005 14:36:06 +0100 (CET)
In-Reply-To: <Pine.NEB.3.96L.1050219122403.67347M-100000@fledge.watson.org>
References: <Pine.NEB.3.96L.1050219122403.67347M-100000@fledge.watson.org>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <1ce55dabd3ee00efb4f717463716be22@sarenet.es>
Content-Transfer-Encoding: 7bit
From: Borja Marcos <borjamar@sarenet.es>
Date: Sat, 19 Feb 2005 14:36:07 +0100
To: Robert Watson <rwatson@FreeBSD.org>
X-Mailer: Apple Mail (2.619.2)
cc: freebsd-hackers@freebsd.org
Subject: Re: High traffic NFS performance and availability problems
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Feb 2005 13:36:08 -0000

> I think leaving the 4.x clients in a known configuration and just 
> varying
> the server configurations the right starting point.  Let's try tracking
> the server 5.x stability/performance first, then look into the client 
> 4.x
> crash reports.

	I've seen amazing performance differences between 4.9 and 5.3 in one 
case: a mail server with Cyrus-imapd and a MySQL database for 
authentication, using fiberchannel disk arrays.

	I couldn't do elaborate benchmarks (it is a production system) but I 
ran into a situation in which 4.9 spent about 90 % of CPU time in 
system (mostly syncer) and, just upgrading to 5.3 the problem 
disappeared.

	In both cases I had tuned some system variables (and I haven't changed 
the variables between 4.9 and 5.3). Notably, I set up a dirhash cache 
of 64 MB, because the machine had lots of huge directories.

	The workload is now the same, and it's working like a charm. The 
machine is a Dell Poweredge 2650 with two CPUs.




	Borja.