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

Biggest objects should not include each other

Moderators: Vladimir Kondratyev, Anton Katilin

Biggest objects should not include each other

Postby sereda » Thu May 11, 2006 7:23 am

Hi there,

I've got a suggestion - let any "biggest object" be not retained by any other biggest object. That just does not make sense to see:

ArrayList -- 9999999999 bytes
Object[] -- 9999999998 bytes

Regards,
Igor
sereda
 
Posts: 15
Joined: Sat Jun 25, 2005 10:33 pm
Location: ALM Works

Return to Java Profiler

Who is online

Users browsing this forum: No registered users and 7 guests

cron