Building Memory-Efficient Java Applications (2009) [pdf]

Re:Building Memory-Efficient Java Applications (2009) [pdf] by dangravell on Tuesday September 01, 2015 @09:43AM (#10152225)

I tend to find the overhead of the JVM appears to contribute the most. If I have -Xmx 128MB for example, around 200MB will often be shown in Windows task manager, or whatever.

Maybe this is addressed in the talk, any my "overhead" is actually my own mis-used data space which I am not aware of.

[ Parent | on HN ]

Re:Building Memory-Efficient Java Applications (2009) [pdf] by jfim on Tuesday September 01, 2015 @10:25AM (#10152526)

The Xmx flag controls the maximum heap size. The JVM has other things that are outside of the heap (the JVM process itself, the code cache, native buffers, resource handles, etc.).

[ Parent | on HN ]

Re:Building Memory-Efficient Java Applications (2009) [pdf] by dangravell on Tuesday September 01, 2015 @11:00AM (#10152761)

That's my point, perhaps clumsily put. It's the stuff outside the heap that appears to take up much of the space.

[ Parent | on HN ]