I can’t help commenting on this thread as well since this is a topic that has buggered me for a while. I have no in-depth knowledge of Windows system internals when it comes to virtual memory, page file and swapping, but I do get the basic picture and I understand the concepts. I have always wondered why on earth Windows swaps out pages from inactive processes even if there is plenty of RAM available. The only effect I see in this is the fact that a machine with 4 GiB such as my development PC behaves like a 10 year old underfurnised office box when I have many windows open and switch to one that was backgrounded for a while.
What annoys me even more is the fact that ‘experts’ keep repeating that this is not the case when it clearly is and strongly advise against disabling the swap file when, as most people who did this reported here, there is no harm in it but in fact a benefit. I have now disabled paging altogether in my machine and it has become extremely snappy and fun to work with. So far, I have not encountered a single problem even while running memory intensive applications.
The only situation I can imagine where this would cause problems is when applications rely on inter-process memory mapping or file mapping. As I understand it, this definitely requires a page file.
Bests - Dietmar