Does windows need to be defragmented regularly?
Why does MacOS not have a Defragmentation utility?
Please teach a detailed person
Super User is a question and answer site for computer enthusiasts and power users. It only takes a minute to sign up.Sign up to join this community
I think the best answer for this comes straight from this apple support KB
About optimization and fragmentation
Disk optimization is a process in which the physical locations of files on a volume are "streamlined." Files and metadata are re-arranged in order to improve data access times and minimize time moving a hard drive's head.
Files can become "fragmented" over time as they are changed and saved and as the volume is filled, with different parts of a single file stored in different locations on a volume. The process of collecting file fragments and putting them "back together" is known as optimization. However, if a failure occurs during optimization, such as power loss, files could become damaged and need to be restored from a backup copy.
Do I need to optimize?
You probably won't need to optimize at all if you use Mac OS X. Here's why:
Hard disk capacity is generally much greater now than a few years ago. With more free space available, the file system doesn't need to fill up every "nook and cranny." Mac OS Extended formatting (HFS Plus) avoids reusing space from deleted files as much as possible, to avoid prematurely filling small areas of recently-freed space.
Mac OS X 10.2 and later includes delayed allocation for Mac OS X Extended-formatted volumes. This allows a number of small allocations to be combined into a single large allocation in one area of the disk.
Fragmentation was often caused by continually appending data to existing files, especially with resource forks. With faster hard drives and better caching, as well as the new application packaging format, many applications simply rewrite the entire file each time. Mac OS X 10.3 Panther can also automatically defragment such slow-growing files. This process is sometimes known as "Hot-File-Adaptive-Clustering."
Aggressive read-ahead and write-behind caching means that minor fragmentation has less effect on perceived system performance.
I suggest also taking a look at Server Fault's answers as well:
My answer on Server fault fits here as well :
It's a bit of a yes, no answer. Useful in certain circumstances but it's less of an issue than it was with FAT or regular HFS. All filesystems will fragment but newer ones are more resistant to fragmenting so badly.
Speaking for Mac OS X specifically HFS+ does a decent enough job of trying to keep things from being fragmented compared to older systems but it still happens just not on the same scale. The OS itself also defrags "small" (20MB or smaller) files on the fly since 10.3 (Panther).
Fragmenting still happens and you can see performance drop because of it, especially in video editing systems or a workflow that requires the ability to read or write large files quickly to the disk. For your standard user - a near non-issue.
The most popular options for defragmenting a hard drive for OS X I've used and run across are:
Cloning the hard drive to another drive and back. This is done using Carbon Copy Cloner or SuperDuper and requires an extra hard drive. If done as part of a backup routine the time hit may not be terrible but it's free to do it this way.
You will need to defragment under certain circumstances - while it's true that Mac OS X eliminates file fragmentation (split files) for files under 20 MB, it doesn't eliminate directory fragmentation (spaces between files). If your drive gets very full >80%, or if you want to install Windows 7 under Boot Camp you may well get an error despite having enough free space as the drive fragmentation prevents the OS from grabbing enough contiguous space.
In my experience iDefrag does a great job - version 2 is out but it's paid software.