In article <slrnkov0v8....@mbp55.local>,
Lewis <g.k...@gmail.com.dontsendmecopies> wrote:
> In message <518f477e$0$52769$
742e...@news.sonic.net>
> Kevin McMurtrie <
mcmu...@pixelmemory.us> wrote:
> > A disk defragmentation utility re-organizes files so that the
> > most recently accessed files are physically close to each other on the
> > platters, as if the whole disk had "hotfiles" optimization.
>
> Unless you install something that constantly monitors your disk, this is
> simply not true. If you DO install something that constantly monitors
> your disk its overhead will almost certainly offset any gains.
>
> This is not the 90s, you do not need to defrag a disk except for very
> limited and specific tasks, (like, streaming raw 4K video from a camera
> or something like that. Maybe. If your disk is slow).
>
> > You'll get
> > back the performance that has been slowly falling away over a period of
> > years.
>
> Yeah, *that's* not true at all. You have to have pretty old hardware
> before you would be able to notice any change at all, and putting in a
> better drive would far outstrip any imagined gains from defragging.
>
> > There's always risk in using defragmentation tools so back
> > everything up first. There's also no need for most users to defragment
> > more often than every year or two.
>
> There's no need for most users to ever defragment. Drives are huge and
> hold millions of megabytes. If your drive is so full that defragging
> would maybe possibly temporarily help, then you need more storage.
There are other kinds of fragmentation. When Apple got rid of Resource
Forks, they switched to an lame trick called packages and bundles.
These are simply directories that some parts of the OS X GUI present as
files. Mail.app has 7711 files and folders in its bundle. Safari has
5620, iCall 3899, and iDVD.app has 9707 files and folders in it. The
Mail.app library may have 20000 to 100000 files in it. Sparsebundle
disk images, by default, contain one file for every 8MB of storage.
That's 2560 files for 20GB. Hotfiles only slightly addresses the problem
of having so many files. Every single software update spreads groups of
related files farther and farther apart. You can have zero fragmented
files but still have extremely slow disk performance due to clusters of
files being physically scattered on a spinning disk. Defragmentation
utilities try to move associated files close together.