Garbage collection in WebSphere Application Server V8, Part 1, Generational as the new default policy

From the developerWorks archives

Chris Bailey, Charlie Gracie, and Karl Taylor

Date archived: April 18, 2019 | First published: June 22, 2011

Not all workloads are created equal. Different applications use memory in different ways and thus can benefit from different garbage collection strategies. The IBM® Java™ Virtual Machine (JVM) has always supported several different GC policies to support various types of applications. At the same time, hardware is evolving and software must adapt to make better use of it. In IBM WebSphere® Application Server V8 the default garbage collection policy uses both generational and concurrent collection strategies. This article provides a brief description of the garbage collection policies available in the IBM JVM, along with a guide for configuring the new default policy. This content is part of the IBM WebSphere Developer Technical Journal.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=681873
ArticleTitle=Garbage collection in WebSphere Application Server V8, Part 1: Generational as the new default policy
publish-date=06222011