Re: High pages/sec, low memory usage on terminal server
- From: "TP" <tperson.knowspamn@xxxxxxxxxxxxxxx>
- Date: Fri, 24 Feb 2006 12:14:51 -0500
Thank you for responding.
I think you are confusing physical RAM with the virtual address
space. The per-process 4GB virtual space is split 2GB for
the process and 2GB for the system. This virtual split is true
regardless of the amount of physical memory in the system.
The above assumes default boot.ini switches.
For example, say we have a Windows 2003 Server with 384MB
of RAM installed. Each process will have the 2GB for the process
and 2GB for the system virtual memory. The 2GB for the system
is shared across all processes. We could have a few people
logged on, each running Word.
The OS decides what pages of the above virtual memory spaces
are actually resident in physical memory versus in the page file. So,
in our example, it will decide which pages of each of the winword.exe
instances' allocated memory pages will actually be resident in RAM.
It does the same thing for all of the other processes running on the
server as well, including system processes. Now, there are certain
things that *must* be resident in RAM at all times, but in general
most of the allocated memory is pageable.
Did I make any sense?
-TP
Patrick Rouse wrote:
http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx
Operating systems based on Microsoft® Windows NT® technologies have
always provided applications with a flat 32-bit virtual address space
that describes 4 gigabytes (GB) of virtual memory. The address space
is usually split so that 2 GB of address space is directly accessible
to the application and the other 2 GB is only accessible to the
Windows executive software.
The 32-bit versions of the Windows® 2000 Advanced Server and Windows
NT Server 4.0, Enterprise Edition, operating systems were the first
versions of Windows to provide applications with a 3-GB flat virtual
address space, with the kernel and executive components using only 1
GB. In response to customer requests, Microsoft has expanded the
availability of this support to the 32-bit version of Windows XP
Professional and all 32-bit versions of Windows Server™ 2003.
.
- References:
- Re: High pages/sec, low memory usage on terminal server
- From: Cláudio Rodrigues
- Re: High pages/sec, low memory usage on terminal server
- From: Patrick Rouse
- Re: High pages/sec, low memory usage on terminal server
- From: TP
- Re: High pages/sec, low memory usage on terminal server
- Prev by Date: Re: Dial Up Client printer problem
- Next by Date: command line
- Previous by thread: Re: High pages/sec, low memory usage on terminal server
- Next by thread: Re: High pages/sec, low memory usage on terminal server
- Index(es):
Relevant Pages
|
