• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows Kernel Question

thescreensavers

thescreensavers

Diamond Member
There is this reg hack that you can put the kernel into ram instead of the Hard drive and virtual memory. How much performance increase can I see by putting the Windows kernel in ram instead of Virtual memory and hard drive??
 
Code can only be executed from memory (ignore some embedded devices that do XIP from flash and stuff) so if the kernel is running it has to be in memory. And since Virtual Memory is just a special way of addressing memory everything in memory is also in virtual memory.

What you're thinking of is the DisablePagingExecutive key and frankly it's pretty much 100% pointless. As I said anything that is running has to be running from memory so only things that have any chance of being evicted from memory are those that you haven't been using like serial port drivers. And have you looked at the size of one of those drivers? I would bet that all of them are under 1M, there are a few exceptions like the nVidia driver on Linux is ~5M but even that's nothing. Guess how long it'll take your system to page back in even 5M worth of data? So even if one of the largest drivers on your system needed paged into memory it would take less than a second to page it back in.

Do you really think MS put all of these little settings hidden in the registry that magically make Windows run faster and turned them off by default?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top