I have been reading up on Microsofts articles with regards to the LARGEADDRESSAWARE and how to turn this on so a 32bit process can take advantage of the extra memory in combination with the boot.ini /3GB switch on the OS.
We have a 3rd party product which seems to be struggling with the workload on the main server and normally hits a peak at around 1GB Physical Memory/ 1.1 GB Virtual Memory on Windows Server 2003 x32 Enterprise Edition. No doubt this causes alot of issues when people are trying to use the server which fails to respond correctly as its out of memory and starts to throw memory exceptions.
Talking with the vendor of the product, they seem quite stubborn and not very willing to change their product or look at issues in helping us overcome this problem, as they believe that its a restriction of the OS and not their product, no doubt this application is storing alot of its data in memory and is hitting a peak at the moment.
I have no options at the moment apart from turning this switch on as I have conducted a small test using a plugin that is loaded by the main server on Windows Server 2003 x32 Edition and x64 Edition which allows the process to acquire alot more memory that it can at the moment.
What are the main issues I should be concerned about if I enable this switch on the process? I believe there are threads that say the 32bit app may not be able to handle addresses greater than 2Gb, I thought a 32bit application could handle 32bit addresses which should really allow it to use 4Gb address space.
Any help is appreciated.