Featured White Papers

• Why choose an Open Source BPM?
• 10 FAQs on Business Process Management
• Best Practices for Getting Started with BPM
• Free Your Devs From The Pain Of Java Redeploys
• Increase Velocity 40% by Using JRebel
• What Developers Want: The End of Application Redeploys
• Developer Productivity Report: Java Tools, Tech, Devs, and Data
• Coding with JRebel: Java Forever Changed
• Utilizing Fast Testing to Transform Java Development
• Do You Really Get Classloaders?
• Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
• Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
• Coding with JRebel, Java Forever Changed
• 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data

Sponsored Links

• APIs for Java Programmers: Manage & Convert DOC, XLS, PPT, PDF & More

• Instantly Preview Java Code Changes: JRebel.com

Sponsored Links

Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs

Memory matters

Discover how much memory an object consumes

By Tony Sintes, JavaWorld.com, 12/28/01

First published on December 28, 2001. Updated on January 10, 2003.

Without buying an expensive memory profile, is there a simple way to see how much memory a Java object consumes?

I don't wish to see the memory allocations in realtime, so I can employ java.lang.Runtime's memory methods.

For instance, I could:

1. Get the total amount of memory available to the VM:

   long totalMem = java.lang.Runtime.freeMemory();
   
   

2. Explicitly set the object in question to null:

   Object myBigObject = null;
   
   

3. Call the garbage collector
4. 
   
5. Subtract:

   System.out.println("You just got rid of " + totalMem - java.lang.Runtime.freeMemory());
   
   

What do you think of this idea?

Unfortunately, you cannot directly determine an object's size. However, in lieu of spending lots of lucre on a profiler, you can crudely approximate the size. While your approach is on the right track, I would change it a bit.

When you instantiate myBigObject and check the memory, the JVM may be performing other activities. So simply creating one object and checking the difference in memory size might be misleading. Instead, you can create a number of objects and take the average of the differences. By taking the average memory size, you can prevent some background JVM activity from overly skewing your results.

The following memory checking main is based upon "Question of the Week No. 107" from the Java Developer Connection:

public class Memory {
    private final static int _SIZE = 500;
    public static void main( String [] args ) throws Exception {
        Object[] array = new Object[_SIZE];
        Runtime.getRuntime().gc();
        long start = Runtime.getRuntime().totalMemory();
        for (int i = 0; i < _SIZE; i++) {
            array[i] = new Object();
        }
        Runtime.getRuntime().gc();
        long end = Runtime.getRuntime().totalMemory();
        long difference = ( start -  end ) / _SIZE;
        System.out.println( difference + " bytes used per object on
average" );
    }
}

Class Memory instantiates 500 Objects and calculates the average memory footprint. Note that I call gc() each time before calling totalMemory(). You cannot force garbage collection; however, it is my hope that the JVM does it so that we can have a cleaner totalMemory() call.

About the author