From owner-freebsd-current@FreeBSD.ORG  Thu Oct 28 04:22:22 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 597E216A4CE
	for <current@freebsd.org>; Thu, 28 Oct 2004 04:22:22 +0000 (GMT)
Received: from harmony.village.org (rover.village.org [168.103.84.182])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AD47643D3F
	for <current@freebsd.org>; Thu, 28 Oct 2004 04:22:21 +0000 (GMT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (harmony.village.org [10.0.0.6])
	by harmony.village.org (8.13.1/8.13.1) with ESMTP id i9S4Lxea073503;
	Wed, 27 Oct 2004 22:21:59 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Wed, 27 Oct 2004 22:22:35 -0600 (MDT)
Message-Id: <20041027.222235.25072396.imp@bsdimp.com>
To: ben@timing.com
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <16767.52483.986921.670394@piglet.timing.com>
References: <16767.52483.986921.670394@piglet.timing.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: current@freebsd.org
Subject: Re: -current NFSv2 and NFSv3 issues
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2004 04:22:22 -0000

In message: <16767.52483.986921.670394@piglet.timing.com>
            Ben Mesander <ben@timing.com> writes:
: things complete succesfully, but buildworld -j1 of -current takes 5
: hours over dedicated 100baseT network, and the ethernet never gets
: even close to being saturated, so the underlying network transport
: doesn't seem to be the bottleneck.

By comparison, it takes 35 minutes on a local disk.  And sometimes,
when there's only one user, it takes 45-55 minutes.  The problem
appears to get worse exponentially with the number of concurrent nfs
requests.

Warner