I have plenty of RAM on my desktop PCs (6 and 8 Gb respectively), so my question was academic and your responses anticipated. This topic is kinda in the same category of " should I use a RAM disk?"
I used to do this back in the days when I didn't have enough RAM to disable the pagefile entirely.
Now, the following quite from Ath makes sense logically:
And forcing the kernel into RAM on a low memory system, so it's even more busy swapping the currently active application in and out of memory, instead of some kernel code you're not using (much) at the moment?
...but the real-world effect was a system that ran somewhat more smoothly. With DisablePagingExecutive enabled, Windows "recovered" faster (with lots less page-in activity) after, say, exiting a memory-hungry game. And I never ran into any adverse effects by having the setting enabled.
Dunno if there'd be any idea of doing it when you've running without pagefile. While there's nothing to page-out to, perhaps the setting could influence whether unmodified code sections are discarded and later page-in'd? *shrug* - not like I'm ever running low on memory on my current rig
But on old systems with limited RAM and slow harddrives? It's worth checking out - depending on how you're using the system, it might be a performance increase.