Date: Tue, 16 Nov 1999 14:56:56 -0500 (EST) From: Zhihui Zhang <zzhang@cs.binghamton.edu> To: Julian Elischer <julian@whistle.com> Cc: Alfred Perlstein <bright@wintelcom.net>, freebsd-fs@FreeBSD.ORG Subject: Re: On-the-fly defragmentation of FFS Message-ID: <Pine.GSO.3.96.991116145429.11223B-100000@sol.cs.binghamton.edu> In-Reply-To: <Pine.BSF.4.10.9911161250040.25805-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 16 Nov 1999, Julian Elischer wrote: > > > > I think you're missing an obvious point, as the file is written out > > the only place where it is likely to be fragmented is the end, hence > > the reason for only defragging the end of the file. :) > > usually, though database files can be written randomly as they are filled > in. > Can a database file has holes? I had some experience with Oracle. I used to create a large file for a database and assumed that all space of the database file are pre-allocated. Otherwise, the performance of the database will be poor. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.96.991116145429.11223B-100000>