Warp2Search.net » News » April 2004 » Understanding Virtual Memory

OSNN have posted a guide about Virtual Memory, very informative!

First off, let us get a couple of things out of the way:

Windows XP is a Virtual Memory Operating system There is nothing you can do to prevent virtual memory There is nothing you can do to prevent paging in the NT kernel



No matter your configuration, with any given amount of ram, you can not reduce the amount of paging by adjusting any user interface in these virtual memory operating systems... you can redirect operating system paging, and you can circumvent virtual memory strategy, but you cannot reduce the amount of paging in the NT family of kernel.

Understanding Virtual Memory

hinkle Unregistered

#53191 Posted on: 04/27/2004 11:54 PM I am truely shocked. This is the first article about how Windows' virtual memory works which is actually correct. All the other articles on the pagefile I've read since I started using Windows 15 years ago have been majorly misinformed and spreading lies like you can disable the pagefile if you have 1gig of RAM or the pagefile should always been 1.5 times your physical RAM which both are completely wrong. I never believed that I would someday read a article from someone who actually understands Windows' virtual memory. I have to keep an eye on this site in the future.

FailedCRC Unregistered

#53193 Posted on: 04/28/2004 12:41 AM you can however, prevent paging OF the NT kernel

isosu Unregistered Posts: 0 Joined: 2007-09-19

#53201 Posted on: 04/28/2004 04:54 AM So what happens if i have a gig of RAM and selected "no paging file"? It doesnt have minimum it simply is not there.

FailedCRC Unregistered

#53214 Posted on: 04/28/2004 12:05 PM if you set it to no paging file then applications can no longer page, although drivers and the kernel still can. If you also prevent the kernel from paging by fiddling the NTExectuivePaging registry key and you run out of memory (in this case it you would only have ram availabale) then you'll get a rather exciting blue screen. thanks to aeden over at aoaforums for some of the above.

perris Unregistered

#53217 Posted on: 04/28/2004 12:46 PM applications can always page regardless of the configuration of your pagefile the os will simply release portions of the code back to the exe or dll this is paging, and you cause more of it when you set your pagefile too small or eliminate it, as you've only prevented the modified pages the ability to go to disc, and you've therefore circumvented memory management strategy...you have not prevented in the least the amount of paging

perris Unregistered

#53218 Posted on: 04/28/2004 12:49 PM if you set your system to no paging file, you've eliminated the ability to release modified pages. when or memory goes under pressure, the os will simply go to the next available candidate for memory reclamation setting the pagefile to no paging file simply redirects and circumvents memory management strategy.

Warp2Search.net » News » April 2004 » Understanding Virtual Memory