Memory settings for Windows using newest bits

Question

Hi All,
I the install guide for this newest set of bits, I suggested memory settings of 1.5GB for the Xmx value. This doesn't work for 32bit Windows.
On Windows, if you bump up the -Xmx, then you cannot use the PermSize parameter.
The heap size is calculated as -Xmx + PermMaxSize. If these two add more than 1408MB then WLS will not start.
Here is the recommendation for Windows 32bit:
set DEFAULT_MEM_ARGS=%DEFAULT_MEM_ARGS% -XX:PermSize=128m
and
Xmx 1024
and
Managed server configuration
If you are using 32bit Windows, please share your experiences.
Heidi.

Answer 1

So, you do not recommend a single instance install on Windows XP? On our local XP machines we had been running single instance because it seemed simpler and it was recommended in the install instructions. On our shared Windows server the managed server configuration was used.
I have been able to run the latest release of the WLS and BPM Workspace on my local XP machine using these settings configured in my setSOADomainEnv.cmd file. It is very SLOW....30 second response time, but it does run. These same settings are not working for everyone else on my team....they are still playing around to find the right answer for their local XP machines.
set DEFAULT_MEM_ARGS=-Xms640m -Xmx768m
set PORT_MEM_ARGS=-Xms768m -Xmx1536m
set DEFAULT_MEM_ARGS=%DEFAULT_MEM_ARGS% -XX:PermSize=128m -XX:MaxPermSize=512m
set PORT_MEM_ARGS=%PORT_MEM_ARGS% -XX:PermSize=256m -XX:MaxPermSize=512m
I have noticed, however, that over time (maybe an hour or so) the admin server starts sending out of memory warnings. So, I have to stop WLS and restart it in order to keep working with reasonable response tiems. Often these out of memory warnings start when it is running but idle.