On Dec 28, 2006, at 6:10 AM, Tim Ellison wrote:
> Thorbjørn Ravn Andersen wrote:
>> Leo Li skrev den 14-09-2006 05:08:
>>> Of course it is possible to limit the java heap so as to force gc
>>> frequently as a workround, is it preferrable to collect short-lived
>>> objects
>>> quickly such as adopt aged-related object queues as one of the gc
>>> strategy?
>>
>> We experimented with this on a Sun box running Sun JDK where one
>> of the
>> more exotic GC's in the server VM used parallel garbage collection
>> without stopping the world for the program executed.
>> This was needed in a large scale J2EE application to avoid user
>> perceptible pauses. ''
>
> This is a common requirement, and there is a whole science around
> optimizing the throughput / speed of the memory manager.
>
> With the greatest of respect to the MM researchers who are making
> great
> progress, the commercial response so far seems to be a bunch of
> heuristics and knobs to tune, e.g. "Understanding the Garbage
> Collector"
> http://publib.boulder.ibm.com/infocenter/javasdk/v5r0/topic/
> com.ibm.java.doc.diagnostics.50/html/contents.html#ToC_27
>
What, you don't believe that "Out of the Box" is an imperative
configuration for enterprise customers? ;)
geir
|