Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some of
the memory being physical memory and some being virtual memory. The more
programs (and therefore more processes) that run, the more memory you
commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically and
performance may be negatively impacted. The Windows 2000 memory manager
uses PAE to provide more physical memory to a program which reduces the
need to swap memory of the page file and results in increased performance.
The program itself is not aware of the actual memory size. All of the
memory management and allocation of the PAE memory is handled by the
memory manager independently of the programs that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able to
have more of its memory remain in physical memory rather than be paged
out, which increases the performance of programs that are capable of using
the /3GB switch. The exception is when the /3GB switch is used in
conjunction with the /PAE switch, the operating system does not use any
memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of physical
memory, the additional physical random access memory (RAM) is not used by
the operating system. Restarting the computer without the /3GB switch
enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the 4
GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's working
set of memory. This process enables memory-intensive programs, such as,
large database systems, to reserve large amounts of physical memory for
data without having to be paged in and out of a pagefile for usage.
Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable to
reserve memory in excess of 4 GB."
======================================================================================================================== >
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne peux
toujours pas utiliser l'API AWE et je n'ai pas eu de reponse concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some of
the memory being physical memory and some being virtual memory. The more
programs (and therefore more processes) that run, the more memory you
commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically and
performance may be negatively impacted. The Windows 2000 memory manager
uses PAE to provide more physical memory to a program which reduces the
need to swap memory of the page file and results in increased performance.
The program itself is not aware of the actual memory size. All of the
memory management and allocation of the PAE memory is handled by the
memory manager independently of the programs that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able to
have more of its memory remain in physical memory rather than be paged
out, which increases the performance of programs that are capable of using
the /3GB switch. The exception is when the /3GB switch is used in
conjunction with the /PAE switch, the operating system does not use any
memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of physical
memory, the additional physical random access memory (RAM) is not used by
the operating system. Restarting the computer without the /3GB switch
enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the 4
GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's working
set of memory. This process enables memory-intensive programs, such as,
large database systems, to reserve large amounts of physical memory for
data without having to be paged in and out of a pagefile for usage.
Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable to
reserve memory in excess of 4 GB."
======================================================================================================================== >
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne peux
toujours pas utiliser l'API AWE et je n'ai pas eu de reponse concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some of
the memory being physical memory and some being virtual memory. The more
programs (and therefore more processes) that run, the more memory you
commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically and
performance may be negatively impacted. The Windows 2000 memory manager
uses PAE to provide more physical memory to a program which reduces the
need to swap memory of the page file and results in increased performance.
The program itself is not aware of the actual memory size. All of the
memory management and allocation of the PAE memory is handled by the
memory manager independently of the programs that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able to
have more of its memory remain in physical memory rather than be paged
out, which increases the performance of programs that are capable of using
the /3GB switch. The exception is when the /3GB switch is used in
conjunction with the /PAE switch, the operating system does not use any
memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of physical
memory, the additional physical random access memory (RAM) is not used by
the operating system. Restarting the computer without the /3GB switch
enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the 4
GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's working
set of memory. This process enables memory-intensive programs, such as,
large database systems, to reserve large amounts of physical memory for
data without having to be paged in and out of a pagefile for usage.
Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable to
reserve memory in excess of 4 GB."
======================================================================================================================== >
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne peux
toujours pas utiliser l'API AWE et je n'ai pas eu de reponse concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
Ma configuration est en 32-bit
"Karim Said-Lalouani" a écrit dans le message
de news: OvCdq%Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some of
the memory being physical memory and some being virtual memory. The more
programs (and therefore more processes) that run, the more memory you
commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically and
performance may be negatively impacted. The Windows 2000 memory manager
uses PAE to provide more physical memory to a program which reduces the
need to swap memory of the page file and results in increased performance.
The program itself is not aware of the actual memory size. All of the
memory management and allocation of the PAE memory is handled by the
memory manager independently of the programs that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able to
have more of its memory remain in physical memory rather than be paged
out, which increases the performance of programs that are capable of using
the /3GB switch. The exception is when the /3GB switch is used in
conjunction with the /PAE switch, the operating system does not use any
memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of physical
memory, the additional physical random access memory (RAM) is not used by
the operating system. Restarting the computer without the /3GB switch
enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the 4
GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's working
set of memory. This process enables memory-intensive programs, such as,
large database systems, to reserve large amounts of physical memory for
data without having to be paged in and out of a pagefile for usage.
Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable to
reserve memory in excess of 4 GB."
======================================================================================================================== >>
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne peux
toujours pas utiliser l'API AWE et je n'ai pas eu de reponse concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
Ma configuration est en 32-bit
"Karim Said-Lalouani" <k_said_lalouani@hotmail.com> a écrit dans le message
de news: OvCdq%23GRHHA.4692@TK2MSFTNGP05.phx.gbl...
Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some of
the memory being physical memory and some being virtual memory. The more
programs (and therefore more processes) that run, the more memory you
commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically and
performance may be negatively impacted. The Windows 2000 memory manager
uses PAE to provide more physical memory to a program which reduces the
need to swap memory of the page file and results in increased performance.
The program itself is not aware of the actual memory size. All of the
memory management and allocation of the PAE memory is handled by the
memory manager independently of the programs that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able to
have more of its memory remain in physical memory rather than be paged
out, which increases the performance of programs that are capable of using
the /3GB switch. The exception is when the /3GB switch is used in
conjunction with the /PAE switch, the operating system does not use any
memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of physical
memory, the additional physical random access memory (RAM) is not used by
the operating system. Restarting the computer without the /3GB switch
enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the 4
GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's working
set of memory. This process enables memory-intensive programs, such as,
large database systems, to reserve large amounts of physical memory for
data without having to be paged in and out of a pagefile for usage.
Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable to
reserve memory in excess of 4 GB."
======================================================================================================================== >>
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne peux
toujours pas utiliser l'API AWE et je n'ai pas eu de reponse concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
Ma configuration est en 32-bit
"Karim Said-Lalouani" a écrit dans le message
de news: OvCdq%Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some of
the memory being physical memory and some being virtual memory. The more
programs (and therefore more processes) that run, the more memory you
commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically and
performance may be negatively impacted. The Windows 2000 memory manager
uses PAE to provide more physical memory to a program which reduces the
need to swap memory of the page file and results in increased performance.
The program itself is not aware of the actual memory size. All of the
memory management and allocation of the PAE memory is handled by the
memory manager independently of the programs that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able to
have more of its memory remain in physical memory rather than be paged
out, which increases the performance of programs that are capable of using
the /3GB switch. The exception is when the /3GB switch is used in
conjunction with the /PAE switch, the operating system does not use any
memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of physical
memory, the additional physical random access memory (RAM) is not used by
the operating system. Restarting the computer without the /3GB switch
enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the 4
GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's working
set of memory. This process enables memory-intensive programs, such as,
large database systems, to reserve large amounts of physical memory for
data without having to be paged in and out of a pagefile for usage.
Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable to
reserve memory in excess of 4 GB."
======================================================================================================================== >>
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne peux
toujours pas utiliser l'API AWE et je n'ai pas eu de reponse concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
Ma configuration est en 32-bit
"Karim Said-Lalouani" a écrit dans le
message de news: OvCdq%Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some
of the memory being physical memory and some being virtual memory. The
more programs (and therefore more processes) that run, the more memory
you commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically
and performance may be negatively impacted. The Windows 2000 memory
manager uses PAE to provide more physical memory to a program which
reduces the need to swap memory of the page file and results in
increased performance. The program itself is not aware of the actual
memory size. All of the memory management and allocation of the PAE
memory is handled by the memory manager independently of the programs
that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able
to have more of its memory remain in physical memory rather than be
paged out, which increases the performance of programs that are capable
of using the /3GB switch. The exception is when the /3GB switch is used
in conjunction with the /PAE switch, the operating system does not use
any memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of
physical memory, the additional physical random access memory (RAM) is
not used by the operating system. Restarting the computer without the
/3GB switch enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the
4 GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's
working set of memory. This process enables memory-intensive programs,
such as, large database systems, to reserve large amounts of physical
memory for data without having to be paged in and out of a pagefile for
usage. Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable
to reserve memory in excess of 4 GB."
======================================================================================================================== >>>
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne
peux toujours pas utiliser l'API AWE et je n'ai pas eu de reponse
concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
y'aurait pas une limitation au niveau du bios ?
--
Pat
Ma configuration est en 32-bit
"Karim Said-Lalouani" <k_said_lalouani@hotmail.com> a écrit dans le
message de news: OvCdq%23GRHHA.4692@TK2MSFTNGP05.phx.gbl...
Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some
of the memory being physical memory and some being virtual memory. The
more programs (and therefore more processes) that run, the more memory
you commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically
and performance may be negatively impacted. The Windows 2000 memory
manager uses PAE to provide more physical memory to a program which
reduces the need to swap memory of the page file and results in
increased performance. The program itself is not aware of the actual
memory size. All of the memory management and allocation of the PAE
memory is handled by the memory manager independently of the programs
that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able
to have more of its memory remain in physical memory rather than be
paged out, which increases the performance of programs that are capable
of using the /3GB switch. The exception is when the /3GB switch is used
in conjunction with the /PAE switch, the operating system does not use
any memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of
physical memory, the additional physical random access memory (RAM) is
not used by the operating system. Restarting the computer without the
/3GB switch enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the
4 GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's
working set of memory. This process enables memory-intensive programs,
such as, large database systems, to reserve large amounts of physical
memory for data without having to be paged in and out of a pagefile for
usage. Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable
to reserve memory in excess of 4 GB."
======================================================================================================================== >>>
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne
peux toujours pas utiliser l'API AWE et je n'ai pas eu de reponse
concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
y'aurait pas une limitation au niveau du bios ?
--
Pat
Ma configuration est en 32-bit
"Karim Said-Lalouani" a écrit dans le
message de news: OvCdq%Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some
of the memory being physical memory and some being virtual memory. The
more programs (and therefore more processes) that run, the more memory
you commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically
and performance may be negatively impacted. The Windows 2000 memory
manager uses PAE to provide more physical memory to a program which
reduces the need to swap memory of the page file and results in
increased performance. The program itself is not aware of the actual
memory size. All of the memory management and allocation of the PAE
memory is handled by the memory manager independently of the programs
that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able
to have more of its memory remain in physical memory rather than be
paged out, which increases the performance of programs that are capable
of using the /3GB switch. The exception is when the /3GB switch is used
in conjunction with the /PAE switch, the operating system does not use
any memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of
physical memory, the additional physical random access memory (RAM) is
not used by the operating system. Restarting the computer without the
/3GB switch enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the
4 GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's
working set of memory. This process enables memory-intensive programs,
such as, large database systems, to reserve large amounts of physical
memory for data without having to be paged in and out of a pagefile for
usage. Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable
to reserve memory in excess of 4 GB."
======================================================================================================================== >>>
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne
peux toujours pas utiliser l'API AWE et je n'ai pas eu de reponse
concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
y'aurait pas une limitation au niveau du bios ?
--
Pat
Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some of
the memory being physical memory and some being virtual memory. The more
programs (and therefore more processes) that run, the more memory you
commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically and
performance may be negatively impacted. The Windows 2000 memory manager
uses PAE to provide more physical memory to a program which reduces the
need to swap memory of the page file and results in increased performance.
The program itself is not aware of the actual memory size. All of the
memory management and allocation of the PAE memory is handled by the
memory manager independently of the programs that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able to
have more of its memory remain in physical memory rather than be paged
out, which increases the performance of programs that are capable of using
the /3GB switch. The exception is when the /3GB switch is used in
conjunction with the /PAE switch, the operating system does not use any
memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of physical
memory, the additional physical random access memory (RAM) is not used by
the operating system. Restarting the computer without the /3GB switch
enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the 4
GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's working
set of memory. This process enables memory-intensive programs, such as,
large database systems, to reserve large amounts of physical memory for
data without having to be paged in and out of a pagefile for usage.
Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable to
reserve memory in excess of 4 GB."
======================================================================================================================== >
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne peux
toujours pas utiliser l'API AWE et je n'ai pas eu de reponse concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some of
the memory being physical memory and some being virtual memory. The more
programs (and therefore more processes) that run, the more memory you
commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically and
performance may be negatively impacted. The Windows 2000 memory manager
uses PAE to provide more physical memory to a program which reduces the
need to swap memory of the page file and results in increased performance.
The program itself is not aware of the actual memory size. All of the
memory management and allocation of the PAE memory is handled by the
memory manager independently of the programs that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able to
have more of its memory remain in physical memory rather than be paged
out, which increases the performance of programs that are capable of using
the /3GB switch. The exception is when the /3GB switch is used in
conjunction with the /PAE switch, the operating system does not use any
memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of physical
memory, the additional physical random access memory (RAM) is not used by
the operating system. Restarting the computer without the /3GB switch
enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the 4
GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's working
set of memory. This process enables memory-intensive programs, such as,
large database systems, to reserve large amounts of physical memory for
data without having to be paged in and out of a pagefile for usage.
Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable to
reserve memory in excess of 4 GB."
======================================================================================================================== >
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne peux
toujours pas utiliser l'API AWE et je n'ai pas eu de reponse concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some of
the memory being physical memory and some being virtual memory. The more
programs (and therefore more processes) that run, the more memory you
commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically and
performance may be negatively impacted. The Windows 2000 memory manager
uses PAE to provide more physical memory to a program which reduces the
need to swap memory of the page file and results in increased performance.
The program itself is not aware of the actual memory size. All of the
memory management and allocation of the PAE memory is handled by the
memory manager independently of the programs that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able to
have more of its memory remain in physical memory rather than be paged
out, which increases the performance of programs that are capable of using
the /3GB switch. The exception is when the /3GB switch is used in
conjunction with the /PAE switch, the operating system does not use any
memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of physical
memory, the additional physical random access memory (RAM) is not used by
the operating system. Restarting the computer without the /3GB switch
enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the 4
GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's working
set of memory. This process enables memory-intensive programs, such as,
large database systems, to reserve large amounts of physical memory for
data without having to be paged in and out of a pagefile for usage.
Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable to
reserve memory in excess of 4 GB."
======================================================================================================================== >
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne peux
toujours pas utiliser l'API AWE et je n'ai pas eu de reponse concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
Bonjour,
je n'avais pas lu tout votre post.
Si vous êtes sur un OS 64 bit, vous n'avez plus besoin du PAE, retirez le
du boot.ini.
PEA était une astuce sur système 32 bit pour étendre l'adressage 32 bit à
36 bit.
Dans votre cas, vous êtes en 64 bit natif.
Quand vous dites, "j'ai demandé à MS", avez-vous un incident ouvert au
support?
Il faut savoir qu'une appli 32 bit sur un OS 64 bit restera limité à un
adressage 32 bit et donc adresage virtuel 4 gb de RAM.
Quand vous dites que "TSE utilise 4GB", que monitorez-vous, et comment?
--
Cordialement,
Emmanuel Dreux.
"Karim Said-Lalouani" wrote in message
news:OvCdq%Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some of
the memory being physical memory and some being virtual memory. The more
programs (and therefore more processes) that run, the more memory you
commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically and
performance may be negatively impacted. The Windows 2000 memory manager
uses PAE to provide more physical memory to a program which reduces the
need to swap memory of the page file and results in increased
performance. The program itself is not aware of the actual memory size.
All of the memory management and allocation of the PAE memory is handled
by the memory manager independently of the programs that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able to
have more of its memory remain in physical memory rather than be paged
out, which increases the performance of programs that are capable of
using the /3GB switch. The exception is when the /3GB switch is used in
conjunction with the /PAE switch, the operating system does not use any
memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of
physical memory, the additional physical random access memory (RAM) is
not used by the operating system. Restarting the computer without the
/3GB switch enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the 4
GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's working
set of memory. This process enables memory-intensive programs, such as,
large database systems, to reserve large amounts of physical memory for
data without having to be paged in and out of a pagefile for usage.
Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable
to reserve memory in excess of 4 GB."
======================================================================================================================== >>
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne
peux toujours pas utiliser l'API AWE et je n'ai pas eu de reponse
concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
Bonjour,
je n'avais pas lu tout votre post.
Si vous êtes sur un OS 64 bit, vous n'avez plus besoin du PAE, retirez le
du boot.ini.
PEA était une astuce sur système 32 bit pour étendre l'adressage 32 bit à
36 bit.
Dans votre cas, vous êtes en 64 bit natif.
Quand vous dites, "j'ai demandé à MS", avez-vous un incident ouvert au
support?
Il faut savoir qu'une appli 32 bit sur un OS 64 bit restera limité à un
adressage 32 bit et donc adresage virtuel 4 gb de RAM.
Quand vous dites que "TSE utilise 4GB", que monitorez-vous, et comment?
--
Cordialement,
Emmanuel Dreux.
"Karim Said-Lalouani" <k_said_lalouani@hotmail.com> wrote in message
news:OvCdq%23GRHHA.4692@TK2MSFTNGP05.phx.gbl...
Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some of
the memory being physical memory and some being virtual memory. The more
programs (and therefore more processes) that run, the more memory you
commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically and
performance may be negatively impacted. The Windows 2000 memory manager
uses PAE to provide more physical memory to a program which reduces the
need to swap memory of the page file and results in increased
performance. The program itself is not aware of the actual memory size.
All of the memory management and allocation of the PAE memory is handled
by the memory manager independently of the programs that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able to
have more of its memory remain in physical memory rather than be paged
out, which increases the performance of programs that are capable of
using the /3GB switch. The exception is when the /3GB switch is used in
conjunction with the /PAE switch, the operating system does not use any
memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of
physical memory, the additional physical random access memory (RAM) is
not used by the operating system. Restarting the computer without the
/3GB switch enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the 4
GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's working
set of memory. This process enables memory-intensive programs, such as,
large database systems, to reserve large amounts of physical memory for
data without having to be paged in and out of a pagefile for usage.
Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable
to reserve memory in excess of 4 GB."
======================================================================================================================== >>
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne
peux toujours pas utiliser l'API AWE et je n'ai pas eu de reponse
concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
Bonjour,
je n'avais pas lu tout votre post.
Si vous êtes sur un OS 64 bit, vous n'avez plus besoin du PAE, retirez le
du boot.ini.
PEA était une astuce sur système 32 bit pour étendre l'adressage 32 bit à
36 bit.
Dans votre cas, vous êtes en 64 bit natif.
Quand vous dites, "j'ai demandé à MS", avez-vous un incident ouvert au
support?
Il faut savoir qu'une appli 32 bit sur un OS 64 bit restera limité à un
adressage 32 bit et donc adresage virtuel 4 gb de RAM.
Quand vous dites que "TSE utilise 4GB", que monitorez-vous, et comment?
--
Cordialement,
Emmanuel Dreux.
"Karim Said-Lalouani" wrote in message
news:OvCdq%Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some of
the memory being physical memory and some being virtual memory. The more
programs (and therefore more processes) that run, the more memory you
commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically and
performance may be negatively impacted. The Windows 2000 memory manager
uses PAE to provide more physical memory to a program which reduces the
need to swap memory of the page file and results in increased
performance. The program itself is not aware of the actual memory size.
All of the memory management and allocation of the PAE memory is handled
by the memory manager independently of the programs that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able to
have more of its memory remain in physical memory rather than be paged
out, which increases the performance of programs that are capable of
using the /3GB switch. The exception is when the /3GB switch is used in
conjunction with the /PAE switch, the operating system does not use any
memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of
physical memory, the additional physical random access memory (RAM) is
not used by the operating system. Restarting the computer without the
/3GB switch enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the 4
GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's working
set of memory. This process enables memory-intensive programs, such as,
large database systems, to reserve large amounts of physical memory for
data without having to be paged in and out of a pagefile for usage.
Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable
to reserve memory in excess of 4 GB."
======================================================================================================================== >>
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne
peux toujours pas utiliser l'API AWE et je n'ai pas eu de reponse
concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
Merci pour vos réponses.
Mon OS est en 32-bit.
Meme avec le /PAE termial serveur n'utilise pas l'API AWE et se limite
donc à une utilistion de 4 GO max.
cdt,
Karim Said-Lalouani
"Emmanuel Dreux [MS]" a écrit dans le
message de news:Bonjour,
je n'avais pas lu tout votre post.
Si vous êtes sur un OS 64 bit, vous n'avez plus besoin du PAE, retirez le
du boot.ini.
PEA était une astuce sur système 32 bit pour étendre l'adressage 32 bit à
36 bit.
Dans votre cas, vous êtes en 64 bit natif.
Quand vous dites, "j'ai demandé à MS", avez-vous un incident ouvert au
support?
Il faut savoir qu'une appli 32 bit sur un OS 64 bit restera limité à un
adressage 32 bit et donc adresage virtuel 4 gb de RAM.
Quand vous dites que "TSE utilise 4GB", que monitorez-vous, et comment?
--
Cordialement,
Emmanuel Dreux.
"Karim Said-Lalouani" wrote in message
news:OvCdq%Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some
of the memory being physical memory and some being virtual memory. The
more programs (and therefore more processes) that run, the more memory
you commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically
and performance may be negatively impacted. The Windows 2000 memory
manager uses PAE to provide more physical memory to a program which
reduces the need to swap memory of the page file and results in
increased performance. The program itself is not aware of the actual
memory size. All of the memory management and allocation of the PAE
memory is handled by the memory manager independently of the programs
that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able
to have more of its memory remain in physical memory rather than be
paged out, which increases the performance of programs that are capable
of using the /3GB switch. The exception is when the /3GB switch is used
in conjunction with the /PAE switch, the operating system does not use
any memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of
physical memory, the additional physical random access memory (RAM) is
not used by the operating system. Restarting the computer without the
/3GB switch enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the
4 GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's
working set of memory. This process enables memory-intensive programs,
such as, large database systems, to reserve large amounts of physical
memory for data without having to be paged in and out of a pagefile for
usage. Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable
to reserve memory in excess of 4 GB."
======================================================================================================================== >>>
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne
peux toujours pas utiliser l'API AWE et je n'ai pas eu de reponse
concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
Merci pour vos réponses.
Mon OS est en 32-bit.
Meme avec le /PAE termial serveur n'utilise pas l'API AWE et se limite
donc à une utilistion de 4 GO max.
cdt,
Karim Said-Lalouani
"Emmanuel Dreux [MS]" <emmanud@online.microsoft.com> a écrit dans le
message de news: uNy9oXqRHHA.4448@TK2MSFTNGP04.phx.gbl...
Bonjour,
je n'avais pas lu tout votre post.
Si vous êtes sur un OS 64 bit, vous n'avez plus besoin du PAE, retirez le
du boot.ini.
PEA était une astuce sur système 32 bit pour étendre l'adressage 32 bit à
36 bit.
Dans votre cas, vous êtes en 64 bit natif.
Quand vous dites, "j'ai demandé à MS", avez-vous un incident ouvert au
support?
Il faut savoir qu'une appli 32 bit sur un OS 64 bit restera limité à un
adressage 32 bit et donc adresage virtuel 4 gb de RAM.
Quand vous dites que "TSE utilise 4GB", que monitorez-vous, et comment?
--
Cordialement,
Emmanuel Dreux.
"Karim Said-Lalouani" <k_said_lalouani@hotmail.com> wrote in message
news:OvCdq%23GRHHA.4692@TK2MSFTNGP05.phx.gbl...
Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some
of the memory being physical memory and some being virtual memory. The
more programs (and therefore more processes) that run, the more memory
you commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically
and performance may be negatively impacted. The Windows 2000 memory
manager uses PAE to provide more physical memory to a program which
reduces the need to swap memory of the page file and results in
increased performance. The program itself is not aware of the actual
memory size. All of the memory management and allocation of the PAE
memory is handled by the memory manager independently of the programs
that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able
to have more of its memory remain in physical memory rather than be
paged out, which increases the performance of programs that are capable
of using the /3GB switch. The exception is when the /3GB switch is used
in conjunction with the /PAE switch, the operating system does not use
any memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of
physical memory, the additional physical random access memory (RAM) is
not used by the operating system. Restarting the computer without the
/3GB switch enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the
4 GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's
working set of memory. This process enables memory-intensive programs,
such as, large database systems, to reserve large amounts of physical
memory for data without having to be paged in and out of a pagefile for
usage. Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable
to reserve memory in excess of 4 GB."
======================================================================================================================== >>>
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne
peux toujours pas utiliser l'API AWE et je n'ai pas eu de reponse
concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani
Merci pour vos réponses.
Mon OS est en 32-bit.
Meme avec le /PAE termial serveur n'utilise pas l'API AWE et se limite
donc à une utilistion de 4 GO max.
cdt,
Karim Said-Lalouani
"Emmanuel Dreux [MS]" a écrit dans le
message de news:Bonjour,
je n'avais pas lu tout votre post.
Si vous êtes sur un OS 64 bit, vous n'avez plus besoin du PAE, retirez le
du boot.ini.
PEA était une astuce sur système 32 bit pour étendre l'adressage 32 bit à
36 bit.
Dans votre cas, vous êtes en 64 bit natif.
Quand vous dites, "j'ai demandé à MS", avez-vous un incident ouvert au
support?
Il faut savoir qu'une appli 32 bit sur un OS 64 bit restera limité à un
adressage 32 bit et donc adresage virtuel 4 gb de RAM.
Quand vous dites que "TSE utilise 4GB", que monitorez-vous, et comment?
--
Cordialement,
Emmanuel Dreux.
"Karim Said-Lalouani" wrote in message
news:OvCdq%Bonjour,
J'ai un probléme avec un serveur Windows server 2003 ENT 64 bit TSE.
J'ai 8 GO de RAM et je remarque que TSE utilise que 4GO max (USER MODE),
meme si le commutateur /PAE est présent dans le boot.ini.
Pour info selon l'article Q277863, qui n'est plus publié chez Microsoft:
"Terminal Services uses 2 GB of address space that is allocated to the
kernel. When you enable the PAE switch, this address space does not
increase because Terminal Services does not make use of the Address
Windows Extensions (AWE) APIs. Therefore, even if your computer has more
than 4 GB of RAM, there is no performance benefit if you use the PAE
switch."
Typically, a process running under Windows 2000 can access up to 2 GB of
memory address space (assuming the /3GB switch was not used) with some
of the memory being physical memory and some being virtual memory. The
more programs (and therefore more processes) that run, the more memory
you commit up to the full 2 GB address space."
When this situation occurs, the paging process increases dramatically
and performance may be negatively impacted. The Windows 2000 memory
manager uses PAE to provide more physical memory to a program which
reduces the need to swap memory of the page file and results in
increased performance. The program itself is not aware of the actual
memory size. All of the memory management and allocation of the PAE
memory is handled by the memory manager independently of the programs
that run."
The preceding information is valid for programs when the /3GB switch is
used. A program that requests 3 GB of memory is more likely to be able
to have more of its memory remain in physical memory rather than be
paged out, which increases the performance of programs that are capable
of using the /3GB switch. The exception is when the /3GB switch is used
in conjunction with the /PAE switch, the operating system does not use
any memory in excess of 16 GB. This behavior is caused by kernel virtual
memory space considerations. Thus, if the system restarts with the /3GB
entry in the Boot.ini file, and the system has more than 16 GB of
physical memory, the additional physical random access memory (RAM) is
not used by the operating system. Restarting the computer without the
/3GB switch enables the use of all of the physical memory."
AWE is a set of application programming interfaces (APIs) to the memory
manager functions that enables programs to address more memory than the
4 GB that is available through standard 32-bit addressing. AWE enables
programs to reserve physical memory as non-paged memory, and then to
dynamically map portions of the non-paged memory to the program's
working set of memory. This process enables memory-intensive programs,
such as, large database systems, to reserve large amounts of physical
memory for data without having to be paged in and out of a pagefile for
usage. Instead, the data is swapped in and out of the
working set and reserved memory is in excess of the 4 GB range.
Additionally, the range of memory in excess of 4 GB is exposed to the
memory manager and the AWE functions by PAE. Without PAE, AWE is unable
to reserve memory in excess of 4 GB."
======================================================================================================================== >>>
J'ai demandé à MS si sous Windows 2003 ENT 64 bit Terminal serveur ne
peux toujours pas utiliser l'API AWE et je n'ai pas eu de reponse
concluante.
Pouvez-vous me dir si vous avez des informations sur le sujet ?
cdt,
Karim Said-Lalouani