Hi,

If you add a timing for pure XSP (without XSLT), you will know where to tune
(XSP or XSLT). Maybe you can report this back also.

In the original mail in the following URL there's something you can try:
 http://www2.real-time.com/pipermail/cocoon-devel/2001-August/010394.html

(try to get the generated source code of one of your XSP, compile it
as a generator and use it as a normal generator instead. [this should
remove the XSP loading/handling phase])

Let us know the result.

HTH,
Michael Homeijer



-----Original Message-----
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: 21-12-2001 9:00 
Subject: cocoon2 performance

Hello
[snip]

Here are the performance results for 500 sequential requests (wget):

normal JSP: 6 seconds
XSP/XSLT: 22 seconds
JSP/XSLT: 133 seconds!!

[snip]

2. is there a way to make XSP even faster (performance tuning)?

[snip]

best regards
- Rainer

---------------------------------------------------------------------
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]>

Reply via email to