Date: Wed, 2 Aug 2006 20:50:57 +1000 (EST) From: Dave Horsfall <dave@horsfall.org> To: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: [PATCH] adding two new options to 'cp' Message-ID: <Pine.BSI.4.61.0608022046450.25291@dave.horsfall.org> In-Reply-To: <20060802073340.GA713@turion.vk2pj.dyndns.org> References: <44CE199C.2020500@centtech.com> <17614.8289.134373.387558@bhuda.mired.org> <96b30c400607310847s1d2f845eo212b234d03f51e9a@mail.gmail.com> <17614.10982.499561.139268@bhuda.mired.org> <ealpn1$lan$1@sea.gmane.org> <20060801072611.GA717@turion.vk2pj.dyndns.org> <20060801171150.GB3413@megan.kiwi-computer.com> <44CF8F1A.5090506@centtech.com> <20060801174048.GE3413@megan.kiwi-computer.com> <44D04797.1040201@freebsd.org> <20060802073340.GA713@turion.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2 Aug 2006, Peter Jeremy wrote: > As a general comment (not addressed to Tim): There _is_ a downside to > sparsifying files. If you take a sparse file and start filling in the > holes, the net result will be very badly fragmented and hence have very > poor sequential I/O performance. If you're never going to update a file > then making it sparse makes sense, if you will be updating it, you will > get better performance by making it non-sparse. Aha! Thanks for that, Peter. -- Dave, wondering why anyone would *not* want sparse files...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.4.61.0608022046450.25291>