Comments on: Force windows to load the kernel in memory http://www.pctipsbox.com/force-windows-to-load-the-kernel-in-memory/ Tips Tricks Central Sun, 08 Nov 2009 16:57:56 +0100 http://wordpress.org/?v=2.8.5 hourly 1 By: Larry Miller http://www.pctipsbox.com/force-windows-to-load-the-kernel-in-memory/comment-page-1/#comment-11872 Larry Miller Wed, 24 Dec 2008 14:22:58 +0000 http://www.pctipsbox.com/force-windows-to-load-the-kernel-in-memory/#comment-11872 LargeSystemCache: This setting is NOT recommended for general use. With rare exceptions this should be used on servers only. It means that memory for caching has priority over memory for application use. This is good for file servers but can kill application performance. This setting is potentially dangerous with some common hardware configurations. It produces an environment that many hardware devices and drivers were not designed for. Some users have reported severe performance problems, system instability, and data corruption. It is deadly with some common video cards amd other devices. DisablePagingExecutive: This setting forces portions of the kernel to remain in RAM at all times, even when they are not needed. Much of the kernel is used ony under relatively rare conditions. By default portions of the kernel are paged in as necessary, then remain in RAM until it is needed for other purposes. Do not impose arbitrary constraints on this activity, it was designed for optimum performance. IOPageLockLimit: Support for this setting was dropped in Windows 2000 SP1. It is not supported on any version of XP or Vista. Contrary to popular opinion, Windows actually manages memory very well on it's own. Do not be misled by the numbers in Task Manager. Some critical values have very diffirent meanings than commonly believed. PF Usage: This is not actual pagefile usage but only potential usage. Actual usage will typically be much lower. Available Memory: The majority of this is not free. It is actually in use by the system or applications, but since it has already been saved to disk it is immediately available if needed. Larry Miller Microsoft MCSA LargeSystemCache:
This setting is NOT recommended for general use. With rare exceptions this should be used on servers only. It means that memory for caching has priority over memory for application use. This is good for file servers but can kill application performance.

This setting is potentially dangerous with some common hardware configurations. It produces an environment that many hardware devices and drivers were not designed for. Some users have reported severe performance problems, system instability, and data corruption. It is deadly with some common video cards amd other devices.

DisablePagingExecutive:
This setting forces portions of the kernel to remain in RAM at all times, even when they are not needed. Much of the kernel is used ony under relatively rare conditions. By default portions of the kernel are paged in as necessary, then remain in RAM until it is needed for other purposes. Do not impose arbitrary constraints on this activity, it was designed for optimum performance.

IOPageLockLimit:
Support for this setting was dropped in Windows 2000 SP1. It is not supported on any version of XP or Vista.

Contrary to popular opinion, Windows actually manages memory very well on it’s own. Do not be misled by the numbers in Task Manager. Some critical values have very diffirent meanings than commonly believed.

PF Usage: This is not actual pagefile usage but only potential usage. Actual usage will typically be much lower.
Available Memory: The majority of this is not free. It is actually in use by the system or applications, but since it has already been saved to disk it is immediately available if needed.

Larry Miller
Microsoft MCSA

]]> By: stooge http://www.pctipsbox.com/force-windows-to-load-the-kernel-in-memory/comment-page-1/#comment-8176 stooge Wed, 06 Feb 2008 23:58:15 +0000 http://www.pctipsbox.com/force-windows-to-load-the-kernel-in-memory/#comment-8176 <p>It has been proved that this tweak is totally useless and does nothing! Here is proof in your own words: "IOPageLockLimit attribute. On some later versions of windows XP that doesn’t exists". That is why M/Soft removed this attribute</p> It has been proved that this tweak is totally useless and does nothing!
Here is proof in your own words:
“IOPageLockLimit attribute. On some later versions of windows XP that doesn’t exists”. That is why M/Soft removed this attribute

]]>