by august1929 » Sun Mar 17, 2013 5:25 am
I have a pretty old and low end rig - ex office computer with a 2 gig processor, reasonable for a year or so ago graphics card (Radeon HD3850 512mb 8x AGP) 2 gig of Ram running on Windows XP.
RW used to be on one of my two internal HDs. Load times were poor, 5 to 10 minutes to get in sometimes, even though I kept the HD defragged and all rubbish cleared. Had to load RW onto an external HD (Western Digital 500 gig running through a USB2 connection) at the Steampipe update as it wouldn't convert on the internal HD (insufficient space).
I thought I would get it updated, clear the internal HD and transfer back from the external HD. Thankfully, I had the sense to make certain RW worked on the external HD before I transferred it back - the load time was extraordinary for my rig - less than two minutes, and only took about 2 minutes to get into a scenario on WCML. This had never been possible on my rig before. In addition, whereas before I had to run without shadows, middle distance etc. RW automatically set itself up to run everything at max, and it ran well with no stutter or lag.
Fast forward a few weeks, and I have loaded all my routes, duplicated mini installations for Europe, US, UK etc. plus other bits and the HD is down to only around 100 gig of free space (because of the duplication) - loads times are going up and up, back to 5 minutes plus into a route and nearly 5 into RW. Looking at the HD, all of the spare space is allocated to the Master File Table (though possibly not used for that yet). Either way, spare space is limited. Defragged the files (you can't defrag MFT) but no appreciable change. Deleted a couple of the pointless mini installations, regaining about 100 gig of space, and hey presto, back to quick load times again.
Thinking on it, is it possible that the compression (or reduction as would have been) of the MFT space could be what is causing the problem. Looking at Microsofts own documentation - "If the unreserved space (i.e. not reserved for MFT) becomes full, space for user files and directories starts to be allocated from the MFT zone competing with the MFT for allocation. If the MFT zone becomes full, space for new MFT entries is allocated from the remainder of the disk, again competing with other files." Reading through, this seems to cause a slow down in file access.
Just a thought - I ain't no techie - but the evidence of my own experience is there and remains - keeping the "file" space as free as possible, plenty of spare without eating into the MFT space, seems to be keeping my fast loading times - even with a low end rig. All this on an external HD through USB2......
Rod
xxxx
xNon partisan rail simmer