Application memory use (original) (raw)

Michael Hall mik3hall at gmail.com
Mon Apr 23 15:11:42 PDT 2012

On Apr 23, 2012, at 4:09 PM, Henri Gomez wrote:

I'm studing on bringing back 32/64 (universal) OpenJDK 7 fo If I'm understanding correctly this would mean by default compressed would be used for both and you should see more or less the same memory footprint. With Compressed Pointers a 64 bits JVM will consume less memory but it will still be higher than a 32 bits JVM for same usage. I'll check when a 32/64 bit openjdk jvm build is available that should match on this option. I built a TestDrive OpenJDK 7 universal (32/64) : http://openjdk-osx-build.googlecode.com/files/OpenJDK-OSX-1.7-x64-u4-jdk-jdk7u4-b21-20120423.dmg Feedbacks welcomed

I'll try it out.

I sort of reproduced what I was seeing earlier in JConsole

http://www195.pair.com/mik3hall/java16.tiff is the java 1.6 run of my app. I hit it with some activity and it goes into the sawtooth pattern I mentioned.

http://www195.pair.com/mik3hall/java17.tiff is the java 1.7 run of the app. After the activity hit memory takes off and climbs 50MB before the next drop.

Who knows might be a problem with something leaking in my app that 1.6 controls better. But 1.7 definitely seems to involve a lot more memory sloshing around.

More information about the macosx-port-dev mailing list