Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Does free space on the hard drive affect performance?
- Thread starter BadWolf13
- Start date
- Sort by reaction score
Yes, it is. If it's too full, you'll notice a performance hit, no matter what computer you're using
Macs are a BSD descendant, and any UNIX that gets more than 90% full with disk space starts to get unhappy file-system wise, as it has less ability to deal with file fragmentation. So, performance suffers because it has to write a file in multiple places, as opposed to one contiguous item.
There is some point where lack of free space will affect performance. I wouldn't say the point is at 10%; 10% free on a 500GB hard drive is quite a lot. But if you have only a few GB free you should do something about it.
There is a completely different effect that will happen with hard drives with _any_ operating system: The tracks on the outside of the hard drive are longer and can contain more data than the tracks on the inside, and therefore reading or writing data on the outside tracks is faster than on the inside tracks. Maximum read speed can be less than half for inside tracks. If you store 250 GB on a 500 GB drive, all the data will be stored on relatively fast tracks; if you squeeze the same data onto a 250 GB drive, both fast tracks on the outside of the drive and slow tracks on the inside of the drive are used.
Thanks guys, that's some good information. One thing I've noticed lately is the DVD Player program crashing, a lot. It always happens when the DVD starts playing. Is the lack of hard drive space a possible cause of that? Or is this totally unconnected?
If the drive is 100% full, then it can't create a swap file which might cause crashes etc. Try another player, VLC for example
I don't think 'having a full hard drive therefore having no room for more swap space' causes crashes. Programs are generally blocked from running until they have their request for more memory fulfilled. This would look like a crash because the program doesn't appear to be running.
If you want to see this affect for yourself, turn off dynamic paging, use up your ram, and then fire up a VM. The VM 'runs' at about a frame a minute.