Many architects hope the G1 and concurrentmarksweep garbage collectors can help Java applications run optimally. The problem: they randomly pause the applications – and as the heap gets bigger, the pauses grow from seconds to minutes. This talk will explore garbage collection in JVMs, the challenges of generic collectors, and how Ehcache solves the problem by managing the cache, figuring out what to keep and toss out, and hiding the cache's contents from the collector. We’ll also consider the implications of Java memory management on scaling. And we’ll demo a huge JVM running with its cache as heap objects versus letting Ehcache manage that same memory while still keeping the data inside the JVM.
Session Detail