cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <>
Subject Re: Performance question
Date Mon, 17 Apr 2000 13:34:29 GMT
XSP pages have to compile the first time through, and that is probably what is
happening.  Was the delay the same for each additional time you accessed the
URL?  For instance, Stefano's presentation took 45 seconds to access from my
own machine the first time (I have a 700 MHz Athlon and 256 MB RAM), but
each additional page rendered in 350-550 milliseconds (I have logging on).

The major problem I have with XSP is similar to the major problem with IIS/
ColdFusion: there are problems with the first access.  XSP takes time to compile

(to be fair, so does JSP), but that is livable.  IIS/ColdFusion ALWAYS returns
a 500 Server Error on the first access, but is OK each additional access (that
not acceptable).  If Cocoon can compile the XSP pages ahead of time, that would
be killer.  Otherwise, write a script to call every XSP page you have and get it

compiled before you have any traffic.

"Schmitt, Christian" wrote:

> Hi,
> I've put together a test application where the source xml document calls the
> SQL processor. This statement returns about 50 rows with 55 columns. Now I
> run the result set thru the XSP processor and do some calculation and
> formatting on around 20 columns of each row. I then apply a xsl stylesheet
> to output HTML.
> Cocoon takes a very long to accomplish that. Most of the time my broweser
> times out. But not from the SQL query (this returns in about 5 seconds).
> What takes so long, is the XSP stage.
> Am I doing something wrong here, or is XSP not intended to work on that kind
> of data?
> Thanks for any info.
> Christian Schmitt
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message