IIS 5 & IIS 6
Is IIS 6.0 PAE/AWE aware?
Last post Mar 04, 2009 02:04 AM by qbernard
Jan 30, 2007 02:16 PM|DarthZar|LINK
Jan 31, 2007 12:41 AM|jcason|LINK
Yes and No.
It really depends on your applications.
If you’re running in a shared environment where you have multiple web applications running in different applications pools, then theoretically yes.
However, keep in mind on the 32 bit platform a single process can only take advantage of 2 GB of private bytes and 2 GB of virtual bites unless you use the 3GB switch.
So for example, if you have 8 application pools that each can safely run in 2 GB per W3WP.
Then if that instance you can take advantage of 16 GB of memory.
But if you have 1 Application pool and it uses a lot of resources in that single W3WP and grows to more than 2 GB of private or virtual bytes, you will get out of memory errors.
So it really depends on how the applications you are using are architected to work in a 32 Bit environment.
Jan 31, 2007 11:32 AM|DarthZar|LINK
Feb 02, 2007 02:07 AM|qbernard|LINK
Dec 28, 2007 03:52 AM|gopi2it|LINK
we are running the application with INPROC mode. so we didnt enable the webgardening (running on only one worker process) due to our code limitation, we can not enable SQL server caching mode. is there any possibility to utilize the 16GB memory.
Server having windows 2003 Ent with 16GB RAM, 3GB enabled
Nov 13, 2008 10:46 AM|JoeStagner|LINK
One of our IIS Gurus asked me to postthe following.
IIS6 is NOT PAE aware.
The w2k3 x86 system will not manage memory above 4GB physical and thus 12 of the 16GB on the machine will not be used
Mar 03, 2009 10:00 AM|jason1625|LINK
This article indicates that the OS will become unstable if the /3GB switch is used on a 32 bit OS. I have seen it in action. Not pretty....
Mar 04, 2009 02:04 AM|qbernard|LINK
That's for 32bit OS, it is Microsoft recommendation to run x64 bit for OS and 32bit for IIS worker process with a max of 2gb ram allocation. Unless your app is x64bit, there is not reason to go 64bit worker process.