“十一五”高中校级领导干部参训情.pptVIP

In 32-Bit Windows, even though a single process can only address up to 4GB of RAM, it is still possible to have Much more RAM than that on a single machine. The slide above depicts the total memory supported by different flavors Of the Windows 2003 operating system. On machines that have more than 4GB of RAM, this memory can still be Taken advantage of by multiple processes, as each process has its own separate address space. This means that If you have two different Oracle instances, each will have its own ‘oracle.exe’, and each oracle.exe will be able to Separately address its own 3GB of user address space. Aside from this, it is also possible for a single process (single oracle.exe) to address memory beyond its 4GB Limit by taking advantage of VLM (Very Large Memory) support on Windows. This is also known as Address Windowing Extensions, or AWE. Oracle takes advantage of Address Windowing Extensions by allowing the database block buffers to Be accessed indirectly through a window in the 3GB address space. The size of this window in the 3GB address Space is defined by the Oracle Registry value: AWE_WINDOW_MEMORY, which defaults to 1GB. Through this window, the rest of the buffer cache, which can be up to 64GB, can be mapped from the extended area of memory. Note#225349.1 discusses the implementation of VLM/AWE on Windows in more detail. * * * Oracle on Windows runs as a single process. As depicted in the slide above, all memory For the Oracle RDBMS on Windows comes out of that single process address space. This memory includes:Process overhead (code for oracle.exe) The SGA for the instance All user threads All user PGA memory The process address space on 32-Bit Windows is 4GB. However, Microsoft reserves 2GB for OS kernel memory, leaving a default of 2GB for a user process (eg ‘oracle.exe’). The /3GB boot switch can be added to the boot.ini to change that dynamic and allow A user process to address 3GB of memory (by restricting the OS/kernel t