Thanks much, guys, for the replies.
We've arrived at the same conclusion that Scott suggests - a GB for the
heap and the other GB for the product (roughly) of the threads and the
stack size in our windows 32-bit environment.
Now it's an exercise in testing the actual -Xss size that we want to
Hi everyone,
We're running Resin 3.0.18 Pro on a Windows 32-bit system and we're
looking to understand/tune our memory settings a bit.
According to http://www.caucho.com/resin-3.0/performance/jvm-tuning.xtp
the stack size is set to 2048k unless set otherwise. Is this true? In
using JConsole
Knut,
Thanks for the info.
Just a check on the math - if Win32 has a 2GB max addressable space,
that includes heap and stack and misc. overhead, right?
If we set resin heap to 1GB and allow each thread to use the 'default'
of 2048k, and we see the number of threads running at about 700, then
On Jan 8, 2009, at 13:52, Jay Ballinger wrote:
Hi everyone,
We're running Resin 3.0.18 Pro on a Windows 32-bit system and we're
looking to understand/tune our memory settings a bit.
According to http://www.caucho.com/resin-3.0/performance/jvm-tuning.xtp
the stack size is set to 2048k
On Jan 8, 2009, at 5:23 PM, Rob Lockstone wrote:
On Jan 8, 2009, at 13:52, Jay Ballinger wrote:
Hi everyone,
We're running Resin 3.0.18 Pro on a Windows 32-bit system and we're
looking to understand/tune our memory settings a bit.
According to
