Hi Jesse,
Thanks for your reply. I'll try bumping up MaxPermSize value - this
is one parameter that can possibly cause the crashes I am observing
(Xms/Xmx are sufficiently high already).
Although I was still hoping there is a way to warm up the stack to
fill in the page cache before the app starts serving requests. But
looks like there's none? (if I can solve the JVM crashing, this
becomes a secondary concern, still would've been a nice performance
enhancement).
Thanks
Andrus
On Apr 24, 2007, at 7:01 PM, Jesse Kuhnert wrote:
It's hard to say for sure what the problem is without more
information but
you can try adding things like the below methods to help your
startup times:
-) Increase or add the initial heap memory size via command line -
Xms224m
(or whatever seems appropriate) .
-) Increase your perm gen space size - this will be critical for
all of the
javassist compilations that happen when initially loading up pages /
components. -XX:MaxPermSize=99m
-) Make sure you don't have caching disabled of course. ;)
Not sure what else there is. I know there are a few unnecessary
synchronized() lock calls in a few places that were added to fix
some issues
related to dev mode problems (ie caching being disabled) - but I've
been
slowly removing them here and there when I notice them. Maybe I
should just
do one big sweep of all usages to be sure.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
