" I highly recommend setting the initial and max page file sizes to the same value anyway. Otherwise, the page file tends to become fragmented, and that really drags down performance. "
I agree totally ! I've long been a proponent of setting the page file minimum to whatever value is expected for maximum at the time I first install the operating system. And depending on drive config, move the page to another drive temporarily, defrag the target drive, and then move the page file back with min=max , that way I'm virtually assured of a page file without any fragmentation issues. Erik Goldoff IT Consultant Systems, Networks, & Security -----Original Message----- From: Ben Scott [mailto:[email protected]] Sent: Wednesday, April 08, 2009 8:49 AM To: NT System Admin Issues Subject: Re: Memory.dmp On Tue, Apr 7, 2009 at 7:39 PM, Sam Cayze <[email protected]> wrote: > I can't find anywhere if it's the initial size, or the max size that > has to be larger than the RAM? I believe it's actually the size of the page file at the time of the crash. :) So, I'd set the initial page file size to RAM+extra. I highly recommend setting the initial and max page file sizes to the same value anyway. Otherwise, the page file tends to become fragmented, and that really drags down performance. Plus the system tends to waste time constantly growing and shrinking[1] the page file, which also drags down performance. [1] Something in the back of my head says that some flavors of Windows only grow during operation, and only shrink at boot, or something like that. Whatever. Some flavors did try to shrink during operation. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
