Does it help to force the kernel into RAM when you've got 16+ GB RAM?

Hi,

So I was reading on the tenforums (as well as elsewhere) that supposedly forcing the windows kernel into RAM increases performance of Windows.

Some of the write ups that I read suggested you only do this if you have an abundance of RAM, but other things I read suggested that the Kernel is already in RAM unless a program/app requires more memory in which case the Kernel is swapped out to virtual ram on the HDD and the real RAM is allocated to the program/app.

So, if you have 16+ GB of RAM, would it improve performance to force the kernel onto RAM or will it simply always be in RAM when you have plenty of free RAM? Looking in task manager I rarely see my computer using more than about 4GB of my 16GB SRAM, unless for certain games that I play that will actually go up as high as about 12GB (with a bunch of added add-ons), so would it be worth looking further into this subject for my use or is it just as likely that the kernel is staying in RAM anyway since I never come close to using 16GB.

Thanks

No those settings of keeping the kernel in RAM was nothing more than myths started way back when. It does nothing. Your best option. Leave Windows to manage itself.

The kernel will always run in RAM. There is no way it could run anywhere else.
The setting in question is "DisablePagingExecutive" in
"HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management"

How that became "load the kernel in RAM" is a mystery to me.

In any modern OS the memory manager will always attempt to keep frequently accessed code and data in RAM and anything else can remain in the original files or the pagefile. If you have a reasonable amount of RAM the memory manager won't have to work very hard to do this. With 16 GB RAM data that was accessed even once could remain in RAM for long periods of time simply because there is no other need for it. This applies to all pageable code and data.

The setting is of no relevance to normal computer users. It may be useful to developers working with device drivers. The amount of memory concerned is quite trivial in a modern OS. I tried the setting experimentally and was unable to detect any significant difference in performance or memory usage. And that was using tools more advanced than Task Manager.

My advice would be to forget about this setting. Most of what has been written about it is wrong. Many people have claimed great performance gains from using it but I suspect they have been influenced by the placebo effect, which incidentally can be very strong.