| guide for analyzing Object allocation [message #511441] |
Mon, 01 February 2010 15:51 |
 Devaraj 
Messages: 2
Registered: February 2010 |
Junior Member |
|
|
Hi,
I am able to profile my application using HeapProf option.
After collecting the data, i am able to open them with Object Allocation or Memory Statistics option.
Now i got the following details.
Class
package
Total Instances
Live Instances
Collected
Total Size
Active Size
can any body guide me, how to analyze these above statistics.
can i assume that Live instances are supposed to be garbage collected, since they are unreachable, they are not garbage collected?
Please let me know, if there is any article to interpret these above results.
regards
Devaraj
|
|
|
| Re: guide for analyzing Object allocation [message #511476 is a reply to message #511441] |
Mon, 01 February 2010 12:02  |
Eugene Chan
Messages: 287
Registered: July 2009 |
Senior Member |
|
|
Hi Devaraj
Here is a quick summary of the columns in the view:
a.. Live Instances: The current number of objects in the heap, of the
specified class, that are presently being utilized (have not been garbage
collected.)
b.. Total Instances: The total number of objects in the heap, which have
been created during the JVM's lifetime (including those that have been
garbage collected).
c.. Active Size (bytes): The total size of all object instances, of the
particular class, that are presently used by the JVM (e.g. have not been
garbage collected.). Note that object-size is JVM implementation dependent.
d.. Total Size (bytes): The total size of all object instances of the
class, including those have been garbage collected earlier in the
application lifecycle.
e.. Average Age: The average age of an object before it is garbage
collected, as measured by the number of garbage collections that this object
has survived. Objects that have survived a large number of garbage
collections are considered to be a memory leak if their usage is no longer
required by the application.
f.. Collected: The total size of objects that has been GC'ed.
Eugene
"Devaraj" <dkommineni@yahoo.com> wrote in message
news:hk6t9f$9pd$1@build.eclipse.org...
> Hi,
> I am able to profile my application using HeapProf option.
> After collecting the data, i am able to open them with Object Allocation
> or Memory Statistics option.
> Now i got the following details.
>
> Class
> package
> Total Instances
> Live Instances
> Collected
> Total Size
> Active Size
>
>
>
> can any body guide me, how to analyze these above statistics.
>
> can i assume that Live instances are supposed to be garbage collected,
> since they are unreachable, they are not garbage collected?
>
> Please let me know, if there is any article to interpret these above
> results.
>
> regards
> Devaraj
>
|
|
|
| Re: guide for analyzing Object allocation [message #511477 is a reply to message #511476] |
Mon, 01 February 2010 12:02 |
Eugene Chan
Messages: 287
Registered: July 2009 |
Senior Member |
|
|
Hi,
Please also check the Help Content which contains more detail about the view
and its content.
Eugene
"Eugene Chan" <ewchan@ca.ibm.com> wrote in message
news:hk706p$r8o$1@build.eclipse.org...
> Hi Devaraj
>
> Here is a quick summary of the columns in the view:
>
>
> a.. Live Instances: The current number of objects in the heap, of the
> specified class, that are presently being utilized (have not been garbage
> collected.)
> b.. Total Instances: The total number of objects in the heap, which have
> been created during the JVM's lifetime (including those that have been
> garbage collected).
> c.. Active Size (bytes): The total size of all object instances, of the
> particular class, that are presently used by the JVM (e.g. have not been
> garbage collected.). Note that object-size is JVM implementation
> dependent.
> d.. Total Size (bytes): The total size of all object instances of the
> class, including those have been garbage collected earlier in the
> application lifecycle.
> e.. Average Age: The average age of an object before it is garbage
> collected, as measured by the number of garbage collections that this
> object has survived. Objects that have survived a large number of garbage
> collections are considered to be a memory leak if their usage is no longer
> required by the application.
> f.. Collected: The total size of objects that has been GC'ed.
>
> Eugene
>
> "Devaraj" <dkommineni@yahoo.com> wrote in message
> news:hk6t9f$9pd$1@build.eclipse.org...
>> Hi,
>> I am able to profile my application using HeapProf option.
>> After collecting the data, i am able to open them with Object Allocation
>> or Memory Statistics option.
>> Now i got the following details.
>>
>> Class
>> package
>> Total Instances
>> Live Instances
>> Collected
>> Total Size
>> Active Size
>>
>>
>>
>> can any body guide me, how to analyze these above statistics.
>>
>> can i assume that Live instances are supposed to be garbage collected,
>> since they are unreachable, they are not garbage collected?
>>
>> Please let me know, if there is any article to interpret these above
>> results.
>>
>> regards
>> Devaraj
>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03477 seconds
] 
Search
Help
Register
Login
Home
