You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Hans-Guenter Stein <Ha...@SiteOS.de> on 2002/02/08 18:34:44 UTC
c2: scales badly compared to c1
I have a c1 application and migrated it to c2.
I have both (c1 and c2) running in the same environment (tomcat 3.3) on
the same machine.
I did a first very basic performance test by just hiting the reload
button of my browser several times very quickly and found:
c1:
single request processing time: 10 ms
multiple requests: 15 ms, 20 ms, 16 ms,...
c2:
single request processing time: 10 ms
multiple requests: 500 ms, 4000 ms, 6000 ms,...
where does it get stuck? is something blocking? how to find out? anyone
with similar experiences?
--
Hans-Günter Stein
Vorstand, SiteOS AG
Weißenfelderstraße 3
85551 Kirchheim/Heimstetten (München)
Tel. +49 - 89 - 90 77 66 00
mail: info@SiteOS.de
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: c2: scales badly compared to c1
Posted by Alexandre Victoor <av...@prisma-presse.com>.
Thanks for your answers guys !!
I look forward to test the next release of cocoon.
Regards
Alex
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
RE: c2: scales badly compared to c1
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Hans-Guenter Stein [mailto:Hans-Guenter.Stein@SiteOS.de]
>
> Vadim Gritsenko wrote:
>
> >
> > In addition to this: Cocoon *requires* tuning in order to make it
work
> > fast. Search for "performance", "tuning" in the users and developers
> > email archives, it was discussed couple of times but not documented.
> >
> > PS: Tuning could be for: memory, high concurrent users load, startup
> > time, etc.
>
> I searched the archives but didn't find any direct hints at all. All I
tried
> so far is to increase those -pool parameters which didn't seem to help
> much...
Some links which might be of help:
Check out thread "Cocoon scalability continued":
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=100996616112144&w=2
Thread "LoadTest":
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99843622402953&w=2
Vadim
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: c2: scales badly compared to c1
Posted by Hans-Guenter Stein <Ha...@SiteOS.de>.
Vadim Gritsenko wrote:
>
> In addition to this: Cocoon *requires* tuning in order to make it work
> fast. Search for "performance", "tuning" in the users and developers
> email archives, it was discussed couple of times but not documented.
>
> PS: Tuning could be for: memory, high concurrent users load, startup
> time, etc.
I searched the archives but didn't find any direct hints at all. All I tried
so far is to increase those -pool parameters which didn't seem to help
much...
>
>
> Vadim
>
> ---------------------------------------------------------------------
> 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: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
--
Hans-Günter Stein
Vorstand, SiteOS AG
Weißenfelderstraße 3
85551 Kirchheim/Heimstetten (München)
Tel. +49 - 89 - 90 77 66 00
mail: info@SiteOS.de
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
RE: c2: scales badly compared to c1
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Stefano Mazzocchi [mailto:stefano@apache.org]
>
> 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).
In addition to this: Cocoon *requires* tuning in order to make it work
fast. Search for "performance", "tuning" in the users and developers
email archives, it was discussed couple of times but not documented.
PS: Tuning could be for: memory, high concurrent users load, startup
time, etc.
Vadim
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: c2: scales badly compared to c1
Posted by Stefano Mazzocchi <st...@apache.org>.
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.
<st...@apache.org> 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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
RE: c2: scales badly compared to c1
Posted by Luca Morandini <l....@tin.it>.
Vishal,
yes, you could match every XML file using the pattern "**/*.xml", and,
if you like, pass every XML file through the same stylesheet.
Best regards,
---------------------------------------------
Luca Morandini
GIS Consultant
lmorandini@ieee.org
http://utenti.tripod.it/lmorandini/index.html
---------------------------------------------
> -----Original Message-----
> From: Vishal.Khatnani@Sun.COM [mailto:Vishal.Khatnani@Sun.COM]
> Sent: Friday, February 08, 2002 7:50 PM
> To: cocoon-users@xml.apache.org
> Subject: Re: c2: scales badly compared to c1
>
>
> In cocoon 1, all xml files were passed to coocon and rendered properly.
>
> However, in cocoon 2, do we need to specify which individual xml
> files we want to pass to cocoon? Can't we just match all xml files?
>
> Thanks in advance,
>
>
> --
> ---------------------
> Vishal Khatnani
> ESIT Group, x40727
> Sun Microsystems Inc.
> Broomfield, Colorado
> ---------------------
>
> ---------------------------------------------------------------------
> 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: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: c2: scales badly compared to c1
Posted by Vishal Khatnani <Vi...@Sun.COM>.
In cocoon 1, all xml files were passed to coocon and rendered properly.
However, in cocoon 2, do we need to specify which individual xml files we want to pass to cocoon? Can't we just match all xml files?
Thanks in advance,
--
---------------------
Vishal Khatnani
ESIT Group, x40727
Sun Microsystems Inc.
Broomfield, Colorado
---------------------
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: c2: scales badly compared to c1
Posted by Alexandre Victoor <av...@prisma-presse.com>.
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...
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 ?
Thanks
Alex
At 18:34 08/02/2002 +0100, you wrote:
>I have a c1 application and migrated it to c2.
>
>I have both (c1 and c2) running in the same environment (tomcat 3.3) on
>the same machine.
>
>I did a first very basic performance test by just hiting the reload
>button of my browser several times very quickly and found:
>
>c1:
>single request processing time: 10 ms
>multiple requests: 15 ms, 20 ms, 16 ms,...
>
>c2:
>single request processing time: 10 ms
>multiple requests: 500 ms, 4000 ms, 6000 ms,...
>
>where does it get stuck? is something blocking? how to find out? anyone
>with similar experiences?
>
>
>
>
>
>--
>Hans-Günter Stein
>Vorstand, SiteOS AG
>Weißenfelderstraße 3
>85551 Kirchheim/Heimstetten (München)
>
>Tel. +49 - 89 - 90 77 66 00
>mail: info@SiteOS.de
>
>
>
>---------------------------------------------------------------------
>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: <co...@xml.apache.org>
>For additional commands, e-mail: <co...@xml.apache.org>
-----------------------
le présent message (ainsi que ses éventuelles pièces jointes) peut
contenir des informations confidentielles. Etant établi à l'intention de ses
destinataires, son utilisation ou diffusion non autorisée est interdite.
Tout message électronique étant susceptible d'altération, Prisma Presse
décline toute responsabilité au titre dudit message en cas de falsification.
Ce message a été traité par un anti virus et aucun virus connu n'a été détecté.
---------------------------------------------------------------------
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: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>