Excessive concurrent-abortable-preclean wall time?

[Eagle Kessler]

Thank you for the explanation, and the confirmation that that was the
correct workaround and settings to use.
I don't that we'll be able to get HotSpot 1.7 deployed any time soon,
but I'll see if we can get bumped up to 1.6 and get some data out of
that.

-- 
Jacob Kessler

On Thu, Oct 15, 2009 at 3:28 PM,  <Y.S.Ramakrishna at sun.com> wrote:
>
>>>
>>> We asked ops to add -XX:MaxTenuringThreshold=2 and
>>> -XX:SurvivorRatio=128, in the hopes that the addition of the tenuring
>>> threshold would prevent the live transient data from being promoted.
>
> This was also exactly the right thing to do to arrest possible fragmentation
> and, in any case, to reduce pressure on the concurrent collector.
>
> -- ramki
>
>> Of course, you sized SurvivorRatio so that all of that transient data
>> (and then some) fitted in the survivor spaces (as your tenuring
>> distribution
>> data below showed).
>