Angelika Schulz schrieb:
Hi Jann,
Running only an hour is not very long for a web application :-) Did you
already increase the heap size for Tomcat using the -Xmx option for the
jvm.
Erm, yes. I am using JAVA_OPTS="-Xms=128 -Xmx=256" ... The machine itself has
1024 MB of memory ... There is no message saying "Out of memory" or "Not
enough heap space", only the CPU is working hard after around an hour,
looking as if it would really have to do loads of jobs.
This could be related to the continuation issue:
https://issues.apache.org/bugzilla/show_bug.cgi?id=43248
https://issues.apache.org/bugzilla/show_bug.cgi?id=44473
https://issues.apache.org/bugzilla/show_bug.cgi?id=44676
The continuations consume quite a lot of memory. They are removed after
a certain period of time, but if the authors visit a lot of the
problematic usecases, continuations can quickly become a problem. If the
application approaches the maximum memory consumption, the garbage
collector is constantly working, which generates quite a lot of CPU
load. This situation will improve in an upcoming release (2.0.2 will be
better, but not perfect yet), we're working on it.
Apart from that, I'd recommend about Xmx=1024 for the application to get
started, and increase that if it's not sufficient. 1024 MB of RAM is
certainly the lower limit for a production server.
You can find Apache Cocoon performance tips at the cocoon website:
http://cocoon.apache.org/2.1/performancetips.html
BTW, here are some more hints:
http://lenya.apache.org/docs/2_0_x/tutorials/production.html
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
