And finally, they claim 'The optimal configuration is to set the minimum and maximum to the same size preventing the OS from resizing the file.' Fact is, you'd rather the OS not have to resize the file, but it won't resize it unless it needs to - and if it needs to, it's better to allow it to do so than to have your apps fail. That's not true either, and even if it were, it wouldn't be a good basis for sizing your paging file. is the amount of memory your system is using at the current moment'.

Such as 'the paging file is used regardless on how much physical RAM is in the system.' (Not so.) And 'the total commit charge. In which we find many of the usual myths repeated. However that message is in fact not triggered unless your pagefile is VERY small or nonexistent. Yes, and? Yes, if your pagefile is too small you'll get the indicated error message. Many people are running just fine with 512 MB or 1 GB of RAM and a pagefile of a few hundred MB.

The only reason why your pagefile would really HAVE to be bigger than RAM, indepdendent of your workload, is to support full memory dumps. OK, VM doesn't HAVE to be bigger, but it really should be.

What happens when you run out of ram