wood burning stoves*
The moose likes Performance and the fly likes JConsole details differ Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » Performance
Bookmark "JConsole details differ " Watch "JConsole details differ " New topic
Author

JConsole details differ

Raja Nagendra Kumar
Greenhorn

Joined: Jun 14, 2008
Posts: 27
Hi,

I see JConsole when launched does show different memory compartments for different applications. When tried with jdk build 1.6.0_14-b08 on jconsole it self it shows the following non heap compartments

1. Memory Pool - Code Cache
2. Memory Pool - Perm Gen
3. Memory Pool - Perm Gen [shared -rw]
4. Memory Pool - Perm Gen [shared -ro]

Where as on a ant build monitoring of my build it shows only two

1. Memory Pool - Code Cache
2. Memory Pool - CMS Perm Gen

Why is such difference.. Looking for a good document to understand more.. Also, I read some where that jdk has tools to jps, jstat, jstatd, jmap, jhat, .. etc.. has any one used these tools successfully in able to find what objects are stored in each of these compartments.. specially navigating from the gcroots down the children.


Regards,
Nagendra

Raja Nagendra Kumar,
C.T.O, www.tejasoft.com
Kees Jan Koster
JavaMonitor Support
Rancher

Joined: Mar 31, 2009
Posts: 251
    
    5
Dear Raja,

That is because the two JVM's use different garbage collector strategies. Read up on JVM GC tuning to see what strategies exist.


Java-monitor, JVM monitoring made easy <- right here on Java Ranch
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JConsole details differ
 
Similar Threads
Some GC usage values in Terracotta server cannot be fetched by Zapcat
View the objects which are getting stored in permgen and total non heap space
JVM Crash
java.lang.OutOfMemoryError: PermGen space
permanent generation shared ro/rw