Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

cs.virginia.edu

Post reply on HN
Print view View original

1–10 of 14 posts

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

#2

Post by cfontes »

IMO This without the talk is not a very usable read. Maybe it's because I've already knew 95% of the concepts it was showing but I felt that the talk must have been pretty interesting as most of the presentation is just bullets points of complex topics.

Does anyone have the audio of it? Also with memory is becoming less of a problem so people tend to completely ignore it, it's nice to see something like this.

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

#7

Post by dangravell »

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.

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

#8

Post by jfim »

dangravell wrote: post #7

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.

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.).

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

#9

Post by dangravell »

jfim wrote: post #8
dangravell wrote: post #7

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.

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.).

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