Fully featured low overhead profiler for Java EE and Java SE platforms.
Performance monitoring and profiling of Jenkins, TeamCity, Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.

Retained size column in object list

Moderators: Vladimir Kondratyev, Anton Katilin

Retained size column in object list

Postby vgritsenko » Tue Jan 25, 2005 5:59 pm

Currently retained size column is featured only in "All Objects", "New Objects" views. I'd suggest to add this column, or provide a way to display this column, for views with objects list ("Instances by class...", "Selected objects", etc).

This would make it incredibly easier to find an offender from the list of hundreds of innocent objects. Currently the only option is to go through each instance and view "Quick info", which is very tiresome, to say the least.
vgritsenko
 
Posts: 26
Joined: Mon Jan 24, 2005 7:29 pm

Postby Vladimir Kondratyev » Tue Jan 25, 2005 7:19 pm

Old versions of profiler (2.0, 2.5, etc) had "retained" size everywhere. Most of the users complained that everything is slow, that seeing running percents when expanding tree node is annoying. That's why we dropped "retained" size from all views excepting "Class tree".

If you want to see retained size of the object (selection, etc), just try to use Crlt+Q (View | Quick Info) action.
Vladimir Kondratyev
 
Posts: 1519
Joined: Tue Aug 10, 2004 7:52 pm
Location: Düsseldorf, Germany

Postby vgritsenko » Tue Jan 25, 2005 7:50 pm

Yes, that's what I said - one can use Quick Info.

But have you tried running Quick Info on 1500 objects in a row? I bet your fingers will tire, don't you think so?

I understand that if it is everywhere it will be slow (it's not amazingly fast now either), but can this be at least an option, when you already have a list of objects, calculate retained sizes for each one of them at a time?
vgritsenko
 
Posts: 26
Joined: Mon Jan 24, 2005 7:29 pm

Postby Vladimir Kondratyev » Wed Jan 26, 2005 8:09 am

But have you tried running Quick Info on 1500 objects in a row? I bet your fingers will tire, don't you think so?


Why don't you use "Class tree" here? This view alows to detect object with maximum retained size in a couple of clicks. Clas list should be used only to check whether instances of particular class present in a memory (the same as Ctrl+N action).

I understand that if it is everywhere it will be slow (it's not amazingly fast now either)


If you have performance problem with profiler please report them.
Vladimir Kondratyev
 
Posts: 1519
Joined: Tue Aug 10, 2004 7:52 pm
Location: Düsseldorf, Germany

Postby vgritsenko » Thu Jan 27, 2005 2:05 am

Vladimir Kondratyev wrote:
But have you tried running Quick Info on 1500 objects in a row? I bet your fingers will tire, don't you think so?


Why don't you use "Class tree" here?


I do. But each line of it shows aggregated numbers for all objects of a class (and "class tree", "class list" going under "statistics" heading for a reason). Now, from all objects of a given class, I'd like to find one or two or three instances which took all the memory (while all of the others don't occupy much).

To make it clear, in my original suggestion I was talking about "object explorer". In there, there is no option to switch on "retained size" column, so one had to go through each one of the thousands of objects to find offending one. That's lots of clicks, takes lots of time.

This view allows to detect object with maximum retained size in a couple of clicks. Clas list should be used only to check whether instances of particular class present in a memory (the same as Ctrl+N action).


May be I'm missing something, but I don't see how to get information on particular object instance in class tree. Object explorer shows instances, class tree does not.

I understand that if it is everywhere it will be slow (it's not amazingly fast now either)


If you have performance problem with profiler please report them.


I had a snapshot from 512Mb JVM which occupied around 620Mb on a harddrive and required 1Gb of RAM to load (yjp.ini: vmargs=-Xmx1024M). YJP would not load it with vmargs=-Xmx900M.

I have 1Gb RAM on this box, and once this snapshot is loaded (and all other applications is killed), it took minutes to expand single "+" in class tree.

Is it expected behavior, or a performance problem?

Just a wild thought, can this be optimized with memory mapped files?
vgritsenko
 
Posts: 26
Joined: Mon Jan 24, 2005 7:29 pm

Postby mathers » Wed Mar 09, 2005 1:48 pm

Vladimir Kondratyev wrote:
But have you tried running Quick Info on 1500 objects in a row? I bet your fingers will tire, don't you think so?


Why don't you use "Class tree" here? This view alows to detect object with maximum retained size in a couple of clicks. Clas list should be used only to check whether instances of particular class present in a memory (the same as Ctrl+N action).


How? If a couple hundred instances exists from one class, then how is it possible to determine which one is the big one?



Ps. Sorry that I opened a new Thread before finding this.
mathers
 
Posts: 3
Joined: Wed Mar 09, 2005 1:21 pm


Return to Java Profiler

Who is online

Users browsing this forum: Google [Bot] and 1 guest

YourKit uses cookies and other tracking technologies to improve your browsing experience on our website, to show you personalized content and targeted ads, to analyze our website traffic, and to understand where our visitors are coming from.

By browsing our website, you consent to our use of cookies and other tracking technologies in accordance with the Privacy Policy.