It is important also to properly size component pools as this affect performance a lot.
If pools are too small comparing to the load, Cocoon will create/destroy components
for each request.
Vadim
> -----Original Message-----
> From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 25, 2001 1:40 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Cocoon2 - bad performance with increasing amount of clients?!
>
>
> Andreas Engfer wrote:
>
> First off, what are your typical response times on the server (recorded in cocoon.log
> as INFO messages).
>
> Also, for production, it is recommended to pregenerate your XSP files, and make
> the appropriate settings in Cocoon.xconf so that the ProgramGenerator does not
> try to compile your XSP and Sitemap.
>
> How does this affect things?
>
> For simple transformations I have seen response times of 20 ms or less
> (if served from cache 0 ms) per page request. I use Tomcat 3.3m4 because
> it is better designed for speed. You may get better results with Caucho's
> Resin.
>
> My machine is an Athlon 750 (you never mentioned the speed of your processor)
> with 256 MB RAM on Win2000 and Sun's JDK 1.3.0_02 HotSpot Server.
>
> I have bombarded my machine with 20 users, and the response time stayed
> around 60ms a request or less (the welcome page on C2 samples).
>
> Also note: make sure you have the "oradb" attribute set to true in your
> <pool-controller/> element for your database settings.
>
> >
> > Hi all,
> >
> > I am testing Cocoon2 with the Distributed Application Tester of IBM and
> > I made some surprising experiences!
> > Start testing my whole application (XSP – Pages, connecting and using an
> > Oracle DB - - - with connection pooling - , applying stylesheets -.xsl -
> > for the rendering of html) with an increasing count of clients -> the
> > average response time grew up linearly with factor two.
> > I assumed that working with the database causes the linear increase of
> > response time. But neither testing the application without database
> > connection, nor testing only the main page of the given examples of
> > cocoon2 were different. Tthe result was the same:
> > Client increase (+1) causes the double average response time. In
> > addition to it even one client needs the whole CPU with a java –
> > process.
> > I guess, with these results Cocoon2 is not usable in a production
> > environment with a large amount of users: the more users - > the longer
> > the response time, starting allready with two users ???!!!
> > Has anyone made the same experiences or can tell me what I made wrong? I
> > would be pleased to hear from you.
> > My system is constituted by Tomcat 3.2 with Cocoon2. My machine (Pentium
> > III, 390 M RAM) is running with Win2000.
> >
> > Regards
> >
> > Andreas
> >
> > ---------------------------------------------------------------------
> > 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]>
---------------------------------------------------------------------
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]>
