• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

filling a partition vs filling a drive

D

dummy2001

Member
I know its best to leave 5-10% of a drive empty, is the same true of partitions within the drive - does it slow things down when they are near capacity as well?
 
If I recall, the defragger wants 15% empty space, or it slows way down. Otherwise, I do not know of any specific need for a certain amount of space.
 
Well, if the partition is nearly full, there is a very good chance that you will start getting much higher levels of fragmentation in new files -- there just isn't that much free space, so what is left is probably fragmented. In terms of fragmentation, it's partitions that count, not physical drives. But for a partition that is used as static storage and is defragmented occasionally, it doesn't really matter how full it is.

FAT32 partitions near maximum capacity can start to have other performance issues... NTFS doesn't really suffer from this.
 
For defragging purposes and normal drive maintenance, a partition is only a virtual drive. Drive rules apply.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top