From owner-freebsd-questions Wed Jan 29 19:25:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA15235 for questions-outgoing; Wed, 29 Jan 1997 19:25:00 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA15219 for ; Wed, 29 Jan 1997 19:24:54 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.4/8.6.12) with SMTP id TAA26343; Wed, 29 Jan 1997 19:24:46 -0800 (PST) Date: Wed, 29 Jan 1997 19:24:46 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Charles Henrich cc: freebsd-questions@freebsd.org Subject: Re: INN .overview and FFS on FreeBSD In-Reply-To: <199701291541.KAA04537@crh.cl.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 29 Jan 1997, Charles Henrich wrote: > 2. (this is more important than #1) Move the .overview files out of > the /var/spool/news hierarchy. > > Does this hold true with FreeBSD? My guess would be yes. The point is made for filesystems in general. While FreeBSD's buffer cache may help you a little bit, the theory applies to any filesystem, DOS, UNIX, you name it. By putting it on a separate disk, the operation can happen concurrently with another operation and doesn't have to wait for the disk to physically seek to the location. The same theory applies to why you spread news spools across disks. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major