Hi,
I'm very satisfied with 5.2.4's performance, fast and use less memory, one
thing I notice is, it uses PermGen faster than 5.1, so if default setting of
PermGen (64mb?) is used, it is fast hitting the Perm Gen out of memory
error, my app uses 90MB PermGen in 5.1, it uses around 105MB in
finding is similar to my tests, here is a table, figures in parentheses are
from 5.2.4, seems Permgen isn't too much difference, heap and classes are a
little more, but not too far from 5.1.0.5, I have an app that's quite high
in traffic, max size for PermGen is set at 256mb, but it uses only
Hi,
I start jvm with -Xms256m -Xmx1024m, and tested my 5.2.4 upgraded app, ran
into this error several times, does that mean 5.2.4 need bigger PermGen
space?
[ERROR] Registry PermGen space
[ERROR] Registry Operations trace:
[ERROR] Registry [ 1] Triggering event 'activate' on m1/Analytics
Angelo,
I think that w/ the changes that were introduced in 5.2 there is indeed
more class generation as a replacement for the javassist usage.. Hence, your
app might need more permgen, which would hopefully be outweighed by the
removal of page pooling in 5.2.
Cheers,
Alex K
On Sun, Jan 9,
From this link:
http://www.mail-archive.com/users@tapestry.apache.org/msg47526.html,
Yes, it seems that Tapestry 5.2 needs bigger PermGen space than
tapestry 5.1
But, tapestry 5.2 use less memory in heap space because no more page pooling.
From this link
