Re: terminalserver 8GB RAM
"Ramon" <ramon@makosoft.nl> schrieb im Newsbeitrag
news:O8z0WEm4IHA.3368@TK2MSFTNGP04.phx.gbl...
> Sorry,
>
> Forgot to mention that we have a 32 bit system.
>
> Ramon
>
> "Ramon" <ramon@makosoft.nl> schreef in bericht
> news:u2yEgLZ4IHA.4448@TK2MSFTNGP05.phx.gbl...
>> Hi,
>>
>> Can anyone explain me if I windows terminalserver 2003 enterprise with
>> 8GB RAM is OK or overdone?
>> Can it be useful?
>>
>> Thx.
>>
>> Ramon
>
32 bit Standard Edition: 4GB physical RAM addressable (software
limitation)
32 bit Enterprise Edition: 64GB physical RAM addressable
Anyway, 32 bit systems do always provide a 32-bit address spaces for
processes. That means for applications, they can commit less than 2 GB
virtual memory, or if you set the /3GB switch in the boot.ini less than 3GB
memory, because they share their space with the kernel. Most apps will be
happy with that. You see in the task manager in the row "virtual memory" how
many bytes got mapped into the address space. The row "physical memory" or
"working set" (not sure about the row name) shows you Windows idea of the
amount of physical memory actually used by the process.
In other words: The system can distribute the whole physical memory, but no
process can have more than this 2GB/3GB directly usable. If that gets a
problem, you must use the 64 bit version, either EMT64 or IA64 (Itanium)
architecture.
-jolt