Home
Large heaps
When the application needs to manage a large amount of data for each partition, then garbage collection might be a factor. A mostly "read" scenario performs well even with large heaps (20 GB or more) if a generational collector is used. However, after the tenure heap fills, a pause proportional to the live heap size and the number of processors on the box occurs. This pause can be large on smaller boxes with large heaps.
Tip: WebSphere eXtreme Scale also supports WebSphere Real Time Java. With WebSphere Real Time Java, the transaction processing response for WebSphere eXtreme Scale is more consistent and predictable, and the impact of garbage collection and thread scheduling is minimized. The impact is reduced to the degree that the standard deviation of response time is less than 10% of regular Java. For more information about WebSphere Real Time, go to the following address: