> MO> Weird... what was the verbose:gc output? Did it correspond with the
> MO> pauses?
>
> Exactly. It's obvious that gc is not that often as it used to be
> without HotSpot. The only problem is that though it's printed out that
> gc took ~0.05msec, in fact rendering freezes for around 1 or 2 secs.
> And such Garbage Collection occur every 3 - 5 seconds. Where the
> problem could be? My current heap size to 128Mb.
Hmm... so far, I haven't found the verbose:gc output to be inaccurate
but 0.05msec seems impossibly fast - did you mean 5 or 50ms? Assuming you
have enough RAM not to start paging[1], the only thing left to recommend is
downloading the eval versions of optimizeit or jprobe[2]and see if you can
see where the time goes.
/Mats
[1] which usually affects gc using programs far worse than other programs,
as the sweep phase of a gc causes the wast majority of pages to be touched...
and the LRU(least-recently-used) algorithm for choosing pages to swap
makes it even worse... even a 10% overdraft can cause the whole program to
be swapped in/out ever gc phase.
[2] www.xxx.com for both of them
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
