Nothinman
Elite Member
- Sep 14, 2001
- 30,672
- 0
- 0
Originally posted by: MrChad
Let Windows manage it.
Just set it to a large fix size, that way you don't have windows resizing the page file every ten minutes.
Yeah, but wouldn't it ideally be better to just set it to a large fixed size, large enough that you don't have to really worry about windows expanding it? Because expanding it would use system resources and generally, when you need to expand the page file, you're not going to exactly have an abundance of system resources.
Just because you are screwed doesn't mean that you should screw yourself more.
but Windows sets a limit of 2gb of virtual memory per application by default and 2gb in general, so you could still run out of virtual memory.
No matter what you do, your system will crash if you need too much virtual memory.
It's just a matter of determining how much you need and setting the page file to a fixed size in order to account for that.
Last time I checked, assuming that an app is coded right is a very bad idea.
And if you have two page files, one in the root directory, and one on a second hard disk and partition, letting Windows dynamically manage the size is not a bad idea because it won't get as fragmented, but otherwise, it's a bad idea.