From owner-freebsd-current Fri Apr 27 21:35:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 684A837B422 for ; Fri, 27 Apr 2001 21:35:24 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id OAA04508; Sat, 28 Apr 2001 14:35:16 +1000 Date: Sat, 28 Apr 2001 14:34:12 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Cejka Rudolf Cc: freebsd-current@FreeBSD.ORG Subject: Re: Experiences with new dir allocation on FFS? In-Reply-To: <20010427192546.A50092@dcse.fee.vutbr.cz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Apr 2001, Cejka Rudolf wrote: > Right now, I have upgraded my -current machine from > February 13 to April 26. > > I were pleased with change to dir allocation in FFS, > but here are my unpleasant test results (UDMA33, partition > is 3 GB where 1 GB is free, soft-updates are enabled): > ... > rm -r is much faster, but tar xvfz is much slower. This is probably caused by write caching now being off by default in the ata driver, possibly amplified by not using soft updates. Without the new dir allocation, -current would be even slower :(. > Furthermore, > it was possible to work on another console in an old system > without any big impact when tar xvfz was run, but on new > system, I have to wait very long time for any disk operation (when > tar xvfz runs). For example, I have to wait from 2 to 30 seconds > on ls -l command. This is also probably caused by write caching not being done. I saw the 2+ seconds hangs on my nfs client when write caching was turned off on the server. I don't know why this is so bad. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message