Originally Posted By: uc50ic4more
Originally Posted By: jrustles
I have the pagefile on it's own dedicated partition FFS!
Having it on its own partition isn't going to help. Its own drive; and preferably on its own SATA channel would help if you really run into trouble; but having it on a partition where the HDD also houses the OS and/ or the user files is not lightening the load of the SATA channel at all. In fact, forcing the read/ write head to skip all over the place to a different partition to mess with the page file might even theoretically slow tihngs down a bit.
I haven't used XP in several years but when I did it was running a recording studio. I had massive HDD throughput requirements and needed a boatload of RAM. I had the OS on a smallish 5,400rpm SATA drive, the audio (upwards of 24 channels of 24 bit, 96KHz audio going in both directions) on another SATA drive (7200rpm: I was always amazed that it never faltered) and the swap was a 4GB SCSI drive (10,000rpm). I found that having all of that HDD activity on entirely separate subsystems was the least of all evils.
I agree with the last part, particularly if one can support that many drives. I have a laptop with only two drive bays, so I do what I can.
Right at this moment, PF is on a separate drive/channel-shared only with music. Solo channel/drive or solo partition all help greatly. The SATA channel bandwidth doesn't help much, it's the fragmentation and queueing
Having everything on one logical drive means that tagged queues are split evenly between virtual memory and system files. Using the following partition structure has really helped my windows:
Partition sizes starting from the fastest outer disc edge (first LBAs) to the slowest (last LBAs) using a 160 and 250GB drive
Drive 1 -160GB
P1 T: - TEMP 4.36GB - FAT32 (PF used to be on here, I think only a small secondary PF is on here now)
P2 C: - SYS - 10.7GB FAT32
P3 D: - Data - 133GB FAT32
Drive 2 -250GB
P1 X: - PAGE - 1.99B FAT(16) with massive 64K sectors
P2 E: - MUSIC - 233GB FAT32
So when the system wants to access the pagefile, the hard drive heads are physically limited to the fastest tracks on the drive, and since they're the longest tracks also, it further reduces head seek activity (but may increase rotational latency).
On the system drive, the TMP partition is first, for the same reason; all my environment variables are set for the T: drive, incl. browser caches, TEMP folder, Scratch disk, Application Settings/Local Settings etc. Therefore the system drive, C: sees the least amount of writing, and it's contents rarely change thus rarely fragment. Also malicious cache/viruses are limited to be written on this drive. The last DATA partition is lowest priority for seek speed and contains bulk data.
One thing XP is struggles with, is running for long periods of time (a month of more) with no reboot. It chokes and stumbles on itself, PF gets so large and fragmented, .logs get out of control- the previous partition structure helps IMMENSELY. The machine goes min. 2 weeks without a reboot (when it does not crash lol)
About the FAT32 I must say that I have never had a HD or FS failure since swearing off NTFS. Before? Happened all the time. FAT32 is bulletproof and not any slower (perhaps faster when dealing with large files).
Thanks for the DisablePagingExecutive suggestion, just checked, found it at 1. Must have been like that for a while. But hey, what kind audio editing did you do? What was your software suite?