Alexandre Victoor wrote:
>
> Hi,
>
> I am also migrating from C1 to C2. I have tried to migrate changing as lessc
> ode as possible. I have noticed that if I use a very basic generator,
> which doesn't use the avalon framework, the amount of memory used by cocoonk
> eep increasing at each request. Well that's quite normal I guess since myg
> enerator can't be recycled...
Yes, you have to use the appropriate Avalon marking interfaces
(Recyclable, etc...) in order to have it recycled. Otherwise, the memory
keeps increasing because new instances of that component has to be
created.
> The real bad thing that I can reproached to C2 is the amount of memory usedb
> y the sitemap. Even with a simple one, about 30MB of memory are used... Ist
> here a way to reduce this amount ?
This memory is not taken up by Cocoon but by Javac since the sitemap
gets compiled. It is likely that 90% of this memory is garbage and will
be collected next time the JVM will need memory and before increasing
the heap size.
Anyway, we are aware of this problem and next release (2.0.2) will
include another java compiler (pizza) which will reduce the amount of
memory used to compile things (both sitemap and XSP) and reduce the
cocoon startup time (since less classes needs to be loaded, the pizza
jar is about 500Kb compared to the 4mb of javac)
Finally: yes, Cocoon 2.x is less polished than Cocoon 1.x but expect
better performances (both runtime and loadtime) and memory footprint (at
startup and under load).
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
