surrealifeIV Posted March 5, 2011 Author Posted March 5, 2011 hello. this sort of sums things up. Definitions: RAM random access memmory ". Virtual memory separates a program’s view of memory from the system’s physical memory, so an operating system decides when and if to store the program’s code and data in physical memory and when to store it in a file. The major advantage of virtual memory is that it allows more processes to execute concurrently than might otherwise fit in physical memory. While virtual memory has limits that are related to physical memory limits, virtual memory has limits that derive from different sources and that are different depending on the consumer. For example, there are virtual memory limits that apply to individual processes that run applications, the operating system, and for the system as a whole. It's important to remember as you read this that virtual memory, as the name implies, has no direct connection with physical memory. Windows assigning the file cache a certain amount of virtual memory does not dictate how much file data it actually caches in physical memory; it can be any amount from none to more than the amount that's addressable via virtual memory."(m.r.techblog wnds trblshoot) he is saying all elements of a computer are given some virtual memmory, or process address space which is used after the commited memmory, which is the amount specific for that application.this space is writeable, and can be reused by the cpu. "Because the address space on 64-bit Windows is much larger than 4GB, something I’ll describe shortly, Windows can give 32-bit processes the maximum 4GB that they can address and use the rest for the operating system’s virtual memory.64-bit processes use 64-bit pointers, so their theoretical maximum address space is 16 exabytes (2^64). However, Windows doesn’t divide the address space evenly between the active process and the system, but instead defines a region in the address space for the process and others for various system memory resources,the file cache, and paged and non-paged pools. final limits related to virtual memory are the maximum size and number of paging files supported by Windows. 32-bit Windows has a maximum paging file size of 16TB (4GB if you for some reason run in non-PAE mode) and 64-bit Windows can having paging files that are up to 16TB in size on x64 and 32TB on IA64. For all versions, Windows supports up to 16 paging files, where each must be on a separate volume. "(m.r.techblog wnds trblshoot) he says in order to get the most out of the physical memmory installed on system with 64* you have to use a sys.cpl, or registry values to change(lower) the cache, and to raise the page, and non-paged pools. commit charge value is commit charge+woking. page file you get miimum by running your computer w/ most or all of the processes you would use, giving you a kind of total system commit charge. max page safe is double that amount. some people run NO page file, leaving windows no writable cache... some like, but leaves no crash dump etc. so, i threw in a pic of cntrlPanel, you'll see it says commit 1gb/32 . but i have 12gb of ram. i have some cache space, and 10.5gb ready, not in backup. now, i have to figure out how to make 32* apps run at least at 4gb, the apps never thought they would get more than 2gb ram ever. peace ref: m russinovich..sysinternals L.R. c.s. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.