Faced with the demands of mission-critical applications, many enterprise
developers have pushed the Java language and the Java Virtual Machine (JVM)
to the limit. The most common issue seen in transactional environments is
achieving predictable response time or latency – in other words, the time
it takes the system to respond to a request or to move a transaction through
the IT infrastructure. In such environments, Garbage Collection (GC) moves
from being a valued feature to a major headache.
Developers respond in different ways to the dilemma of GC-induced pauses. For
example, a developer working for a financial services firm could set up
application environments with enough memory at the beginning of each trading
day to avoid encountering GC until the markets close, wh... (more)