Run ASP.NET application as LARGEADDRESSAWARE

[Thomas Lykke Petersen]

The setup is a Windows 2003 Server (Standard) with the /4GT (/3GB)
switch turned on which should enable ~3GB of memory for user processes
and only ~1GB for windows processes.

Is it possible to make an ASP.NET application utilize the new found
memory or should the ASP.NET application be build with the
LARGEADDRESSAWARE bit turned on?

Is the CLR / IIS / aspnet_wp.exe LARGEADDRESSAWARE compatible? Is it
the parent process which determines whether the processes spawned by
this can utilize the memory in the new address space?

I hope someone has some answers to clarify this issue for me.
Thanks in advance.

Regards,
Thomas Lykke Petersen

[Bruce Barker]

on 32bit machines there is 4gb of virtual address space. the default
implementation of nt is to divide the addrss space in half, 2gb for the os
2gb per user process. the /3gb switch tells the o/s to only have 1gb, thus
allowing any user process on the machine to have 3bg of virtual address
space available. no special code is required.

this is different than the AWE option which allows addressing more than 4gb
of virtual memeory, which does require special code support.

because asp.net has a lot of code checking resource limits you may run into
bugs with the /3gb switch on.

note: currently asp.net has a bug where if the machine has over 2gb of
physical memory the GC burns cpu. be sure to get the hotfix (you will need
to open a support call).

-- bruce (sqlwork.com)

"Thomas Lykke Petersen" <th*******************@gmail.com> wrote in message
news:a9**************************@posting.google.c om...

The setup is a Windows 2003 Server (Standard) with the /4GT (/3GB)
switch turned on which should enable ~3GB of memory for user processes
and only ~1GB for windows processes.

Is it possible to make an ASP.NET application utilize the new found
memory or should the ASP.NET application be build with the
LARGEADDRESSAWARE bit turned on?

Is the CLR / IIS / aspnet_wp.exe LARGEADDRESSAWARE compatible? Is it
the parent process which determines whether the processes spawned by
this can utilize the memory in the new address space?

I hope someone has some answers to clarify this issue for me.
Thanks in advance.

Regards,
Thomas Lykke Petersen

[Thomas Lykke Petersen]

Thank you for the quick reply. Though, it didn't quite make it clear
for me whether ASP.NET would be allowed to allocate memory from the
new address space created by the /3gb switch?

"Bruce Barker" <br******************@safeco.com> wrote in message news:<uM**************@TK2MSFTNGP12.phx.gbl>...

on 32bit machines there is 4gb of virtual address space. the default
implementation of nt is to divide the addrss space in half, 2gb for the os
2gb per user process. the /3gb switch tells the o/s to only have 1gb, thus
allowing any user process on the machine to have 3bg of virtual address
space available. no special code is required.

this is different than the AWE option which allows addressing more than 4gb
of virtual memeory, which does require special code support.

because asp.net has a lot of code checking resource limits you may run into
bugs with the /3gb switch on.

note: currently asp.net has a bug where if the machine has over 2gb of
physical memory the GC burns cpu. be sure to get the hotfix (you will need
to open a support call).

-- bruce (sqlwork.com)