Swap file stuff ...
Over time, I've embraced and subsequently rejected many opinions about swap files.
Currently my swap file is located on the outermost tracks of my (physical) disk. This is the C: partition. The outside tracks enable the speediest data transfers. In most cases, when my disk is called into action, I'm expecting some delay. Starting a program, loading or saving work, exercising an obscure option, or switching from window to window all cause some disk activity, and any delays resulting from this are expected and bring a minimal disturbance to the normal flow of my work.
Swap-file activity often takes place as my system substitutes disk storage for RAM storage. Since this can, and often does, occur when I'm expecting, or desiring, lightening responses from my system, I find the delay all the more distruptive; hence, my desire to minimalize it. This lead me to locating this file for maximum speed.
To reduce disk-head movement, and the accompanying delays, I set the minimum swap file size to the maximum size Windows would select during my typical work session. This file now has squatter's rights on prime disk surface real-estate, and is much less likely to become fragmented. As a precaution against compromising any sudden and unexpected bursts of ambition on my part by inadequate virtual memory, my swap file has no upper limit. (Beyond the capacity of my disk.)
Segregating a swap file to its own partition has the attraction of allowing it to expand and contract without concern for keeping off the toes of other data, since one can usually dance faster in an empty room. A separate partition can also exploit a larger cluster size, reducing overhead when dealing with huge files. Also, the benefits of simplicity cannot be dismissed: We know Windows suffers from the handicap of being complex.
Have a great new year.
Cheers, PW. |
