Confused on result of the implementation for testing object memory consumption in java

Question

I use the below implemenatation to test the memory consumption of the java objects.
But it prints usage as 104936 B when the i limit is from 384 to 1694 in the calling method's for loop.
It prints usage as 0B for when the above i limit is less than 384.

Why is this?

IDE : eclipse kepler
java : 1.5 (this acts differently when the java version is also changed)

OS : Ubuntu 12.10

public static void main(String[] args) {

    Runtime runtime     = Runtime.getRuntime();

    long totalStart     = runtime.totalMemory();
    long start          = runtime.freeMemory();

    SampleTester sampleTester = new SampleTester();
    sampleTester.callingMethod();

    long totalEnd       = runtime.totalMemory();
    long end            = runtime.freeMemory();

    System.out.println("Usage [(("+totalEnd+"-"+end+") - ("+totalStart+"-"+start+"))] \t: " + ((totalEnd-end) - (totalStart-start)));

}

private void callingMethod(){

    for(int i = 0;  i < 1694; i++){

        ArrayList<String> arrayList = new ArrayList<String>();

    }
}

possible duplicate of [What is the memory consumption of an object in Java?](http://stackoverflow.com/questions/258120/what-is-the-memory-consumption-of-an-object-in-java) — RamonBoza, Oct 17 '13 at 12:27

Joachim Sauer · Accepted Answer · 2013-10-17T12:44:56.423

Each ArrayList you create is immediately eligible for GC when the current loop iteration ends.

So theoretically the JVM could allocate each ArrayList in the space formerly occupied by the one from the last iteration and only need one "slot", which gets discarded when the last iteration ends and the method exists.

That explains the "0" value (this or a similar optimization).

In practice, the JVM doesn't always do that, but will leave eligible object uncollected for some time in order to be more performant (because doing GC too often can be just as bad for performance).

When and how the JVM decides which optimization to apply is entirely implementation-defined and knowing the very details is rarely useful information (because you can't depend on it and it can change with the next version).

So if you want to find out how much memory n ArrayList object need, make sure that you each one of those is actually reachable and as such not eligible for garbage collection when you check the current used memory.

Confused on result of the implementation for testing object memory consumption in java

1 Answers1