This section is now closed.
-
steve
- Site Admin
- Posts: 81627
- Joined: Sat Dec 01, 2007 11:43 am
- Operating System: Linux *buntu
Post
by steve » Sun Aug 10, 2008 1:58 pm
In relation to MDOC's comments about the swap file - I think that Windows reports free space taking into account the swap file (it counts the swap file as used space), but by default, Windows controls the swap file size dynamically depending on memory usage. When you get to very low available space in ram and disk space, then the exact amount of free disk space can rapidly go up or down as Windows tries to manage the limited resources and performance will suffer while Windows is doing this.
So yes, 10% free is just a "rule of thumb" rather than a precise amount, but Windows performance and stability can be severely affected by low disk space. Also, disk fragmentation occurs much more rapidly when there is little free space.
BTW I enjoyed your nail biting account of running close to edge jan.kolar
-
MDOC
- Posts: 53
- Joined: Thu Jul 10, 2008 4:52 am
- Operating System: Please select
Post
by MDOC » Sun Aug 10, 2008 4:21 pm
Yes, virtual memory allocation was the wrong term, I'd realized.
-
kozikowski
- Forum Staff
- Posts: 69374
- Joined: Thu Aug 02, 2007 5:57 pm
- Operating System: macOS 10.13 High Sierra
Post
by kozikowski » Sun Aug 10, 2008 7:27 pm
<<<So yes, 10% free is just a "rule of thumb" rather than a precise amount, but Windows performance and stability can be severely affected by low disk space.>>>
And not just Windows. We have one video cowboy that likes to run close to the edge. Every so often he starts a process that needs 100.5% of the drive space he has and his Mac gags and chokes.
It's fun to watch a Linux machine run out of drive space. Its eyes roll up and it starts blowing spit bubbles.
Both machine types start getting nervous right around the 10% point.
I get out the fire extinguisher from under my desk...
Koz
