Hotspot vs. virtual memory
August 8, 2008 3 Comments
Dear Lazyweb. It seems to me that (on the Hotspot VM) the Java heap is always kept in RAM and never swapped out, because the GC is continually accessing the memory. For example, if I have Firefox, Evolution and Eclipse running, and then start a compilation that takes a lot of memory, Firefox and Evolution get swapped out, while Eclipse (which takes up around 1G on my machine) stays in memory all the time, thus effectively stealing memory from the compilation process. Has anybody else observed this too? Is my diagnosis correct? Is there a way to fix this? Would be nice if Java programs behave similar to other programs and don’t lead the virtual memory system ad absurdum.