Java engine Memory Management

Do not set exceptionally high max heap value for Java server process !

The reason why big heaps (4g for example) are not recommended is that the bigger the heap the longer it takes for the garbage collector to run through it. So there is a trade off between less gc-s in the beginning when the JVM is started and much longer ones, when the heap is for example half full. Therefore, larger max heap doesnt related to better performance. If you have huge resource, you add more server nodes you can scale more easily and serve a larger number of users.

a. 723909 – Java VM settings for J2EE 6.40/7.0
b. 876722 – Java heap size doesn’t update or appears twice in cofig tool

Advertisement

~ by onnry on July 9, 2008.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Connecting to %s

 
Follow

Get every new post delivered to your Inbox.