The max heap (set with the -Xmx parameter) is shared between all
generations, with
the typical Sun/Oracle JVM that is eden, survivor, tenured and permanent
generations.
The JVM usually does a pretty good job at adjusting the individual sizes
according to
how much garbage your app produces.
I
Hi Knut,
Thanks a lot for the feed back.
When you say If your app was faster you would see fewer threads and
hence less memory used. are you thinking we need to make our app. more
efficient or throw some CPU power at it?
Thanks,
Keith
On 10/30/2012 11:11 AM, Knut Forkalsrud wrote:
The max
On 10/30/12 10:14 AM, Keith Fetterman wrote:
Hi Everyone,
I could use a little help troubleshooting some messages in my
jvm-default.log. I am seeing a lot of the following messages in our
Resin logs. We are currently running Resin 4.0.23 Pro.
INFO com.caucho.env.health.HealthService
Thanks Scott,
We are currently running 4.0.23 Pro. I am getting ready to deploy
4.0.32 Pro into production. Do you think the reporting in 4.0.32 Pro is
better and would help troubleshoot the problem?
Keith
On 10/30/2012 02:04 PM, Scott Ferguson wrote:
On 10/30/12 10:14 AM, Keith Fetterman
On 10/30/12 4:23 PM, Keith Fetterman wrote:
Thanks Scott,
We are currently running 4.0.23 Pro. I am getting ready to deploy
4.0.32 Pro into production. Do you think the reporting in 4.0.32 Pro is
better and would help troubleshoot the problem?
It should be about the same. The 4.0.23 heap
