JVM garbage collection behaviour on virtual machines

Interesting blog about how multiple virtual machines running on the same metal, each with their own JVM instances performing garbage collection can degrade app performance when the hypervisor has to swap out memory

http://www.devwebsphere.com/devwebsphere/2009/08/why-you-shouldnt-overcommit-memory-on-virtualized-servers-running-java.html

Given at work, we will be switching platforms so everything is moving to the supposedly common good of redundancy that virtualisation provides, its worth noting.  I wonder if the new G1 garbage collector is any different, or if staying on Solaris with its Sun/Java roots and using zones instead manage this any differently?

Leave a Reply