protectuf.blogg.se

Some of the bigger files are in 600+ fragments. Tons of "under 20 MB" files were in lots of pieces. Well, looks like plenty of fragmented files to me. I thought Mac OS X was supposed to auto-defrag things? Keep in mind that * RED * means fragmented files. Just like that 340 Meg hard drive I got in 1994 would never fill up!) Some stupidity about how hard drives in general are so big and so fast, they don't need to be defragged. But no information on when it happens, how to do it manually, etc. Strange information about Mac OS X actually auto-defragging files under 20MB. (And this is easier than just running a defrag?) Apple's own website recommended backing up your applications and files, formatting, re-installing the OS, and then restoring your applications and files if you wanted to restore performance. Macs "don't need to be defragmented" was one thing mentioned over and over and OVER. I couldn't find a lot of good information. Nothing visible under User Accounts.Ģ) I ran fsck and ran a permissions repair. Since it's a Mac, things are a little different.ġ) I checked for startup items. If this were a Windows system, I'd would have done three things on it right away: Application launching seemed to take forever. Performance on it seemed poorer than I expected it to be. Its hard drive was a Fujitsu 120 Gig, 5400 RPM w/ 8 Megs Cache. True, Mac OS X may work with files better than Windows XP does, but fragmentation still happens.

I've seen many Mac users claim that Macs don't suffer from fragmentation. And they suffer the same performance degradation caused by hard drive fragmentation. Macs use the same hardware Windows PC use. MyDefrag (was JkDefrag), Defraggler, Auslogic's Defrag, Contig, and Power Defragmenter (a GUI for Contig) are all free defragmentation tools, for Windows. Well, that's how it works in Windows at least. These re-arrange files to put things back together. That's why there are defragging applications. Having one, contiguous block for each file helps the hard drive load the file quicker. So having split-second delays over and over added for every single file access can cause noticeably longer system startup and program launching. It doesn't take too long for the drive to do that with a single file, but your system is usually trying to access dozens or hundreds of files at the same time. Instead of just simply loading your files, your hard drive has to search all over the physical drive surface for the pieces of the file. On a mechanical hard drive, having fragmented files slows things down. They end up in pieces, and new files end up getting broken up as they are written to the free spots between the pieces of the older files.

This in inevitable.įiles get written and re-written, added to and moved. Because of how disk storage works, fragmentation happens.