From owner-freebsd-current@FreeBSD.ORG Wed Oct 27 16:33:51 2004 Return-Path: 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 C3CC116A4CE for ; Wed, 27 Oct 2004 16:33:51 +0000 (GMT) Received: from imf21aec.mail.bellsouth.net (imf21aec.mail.bellsouth.net [205.152.59.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F89543D60 for ; Wed, 27 Oct 2004 16:33:51 +0000 (GMT) (envelope-from ahze@ahze.net) Received: from [192.168.1.5] ([68.209.163.3]) by imf21aec.mail.bellsouth.netESMTP <20041027163350.DTGP2451.imf21aec.mail.bellsouth.net@[192.168.1.5]>; Wed, 27 Oct 2004 12:33:50 -0400 In-Reply-To: <16767.52483.986921.670394@piglet.timing.com> References: <16767.52483.986921.670394@piglet.timing.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Michael Johnson Date: Wed, 27 Oct 2004 12:33:46 -0400 To: Ben Mesander X-Mailer: Apple Mail (2.619) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 16:33:51 -0000 For a lan NFSv3/UDP is by far the fastest and is much faster than NFSv2 Michael On Oct 27, 2004, at 12:29 PM, Ben Mesander wrote: > Hi all, > > We're seeing some data corruption and performance problems here with > NFSv3/TCP on a machine running -current NFS client against a 4.8 NFS > server. > > The problems can be reproduced by doing a 'make buildworld' over > NFS. With NFSv2 & UDP we could buildworld with -j8 and the build > would usually - but not always - complete successfully. The times when > it did not appeared to possibly be a result of the mtime.tv_usec not > being checked for files over NFS (ie, one build step creates a .depend > file, and another step tries to use it before it "appears" over NFS). > > We decided to try NFSv3/TCP to see if we could get better > performance. However with buildworld and -j8, we reliably see gcc or > some other toolchain component coredump during the build. With -j1 > 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. > > We appear to have sufficient nfsd's & nfsiod's in that they don't > all seem to be incurring appreciable CPU time. > > Any clues as to the data corruption issue? Should we expect NFSv3 over > TCP to outperform NFSv2 over UDP? > > Thanks, > Ben > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org"