From owner-freebsd-arch Thu Nov 2 13:58: 2 2000 Delivered-To: freebsd-arch@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E005837B4CF for ; Thu, 2 Nov 2000 13:57:58 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eA2Lvs814424; Thu, 2 Nov 2000 13:57:54 -0800 (PST) Date: Thu, 2 Nov 2000 13:57:54 -0800 From: Alfred Perlstein To: Matt Dillon Cc: Marius Bendiksen , Randell Jesup , arch@FreeBSD.ORG Subject: Re: Like to commit my diskprep Message-ID: <20001102135754.Y20567@fw.wintelcom.net> References: <200011021725.eA2HPeM38718@earth.backplane.com> <20001102132140.W20567@fw.wintelcom.net> <200011022135.eA2LZA740940@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200011022135.eA2LZA740940@earth.backplane.com>; from dillon@earth.backplane.com on Thu, Nov 02, 2000 at 01:35:10PM -0800 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matt Dillon [001102 13:36] wrote: > > : > :* Marius Bendiksen [001102 13:19] wrote: > :> > Not to mention the bytes/inode (-i) If you want fsck to go fast on a > :> > big filesystem, reducing the number of inodes helps a lot. I find myself > :> > using -i 32768 or -i 65536 or even higher numbers on partitions which > :> > hold big database files. > :> > :> FFS is woefully inadequate at handling databases, due to the block > :> indirection, but e.g. Oracle will allow you to run directly on top > :> of a device. > : > :Block indirection could be optimized by attempting to allocate > :indirect blocks in the same area as either the inode or datablocks > :that the indirect blocks address. > > Indirect blocks aren't relevant if you are using a large block size, > because there are few enough of them the OS has no problem caching > them. the problem isn't caching them, it's fsyncing them during appends that cause additinal disk seeks. But that's not exactly a deadly problem, just a little suboptimal. it's also fsyncs on newly created files that can cause problems. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message