Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Message-Id: <00a401c00844$bdb66720$6d2853c3@sop.cstb.fr>
From: "Olivier Richaud" <richaud@cstb.fr>
To: <cocoon-users@xml.apache.org>
References: <001601c00704$d3e46c40$7d01a8c0@windebt.com>
 <399A86B1.9B1B98AF@infoplanning.com>
 <00f901c00780$27547a70$6d2853c3@sop.cstb.fr>
Subject: speed problems [ADVICE NEEDED]
Date: Thu, 17 Aug 2000 14:14:49 +0200
Organization: CSTB
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

Sorry, but I'm posting again the same message. Matthew Smith noticed
yesterday that compilation was really slow and after too. I have the same
problem with XSP pages producing XML code to be parsed by and XSL
stylesheet. Someone pointed some optimisations for Xalan, and I went to
Xalan's page. They are talking about XSLTProcessor configured to use SAX
instead of DOM... They are assessing it can speed up Xalan. Is this relevant
in the case of Cocoon?

More generally, I concerned with performances and I would appreciate any
hint in order to speed up Cocoon while using XSP. I tried, among other
things, to deactivate caching. I must say I'm not convinced and I have no
opinion. Most of my pages are dynamic and I don't know if I can benefit from
Cocoon's caching.

Thanks in advance for any help and opinion.

Olivier Richaud
CSTB
office: +33 4 93 95 67 24
mobile: +33 6 87 52 53 17
www: http://cic.cstb.fr
----- Message d'origine -----
De : Olivier Richaud <richaud@cstb.fr>
� : <cocoon-users@xml.apache.org>
Envoy� : mercredi 16 ao�t 2000 14:47
Objet : Re: speed problems


> > Matthew Smith wrote:
> > >
> > >         I've noticed my pages loading slowly, but I've just been
playing
> with very
> > > very simple stuff so far.  I loaded up an example produced in this
> forum,
> > > Logic and Layout TagLibs basic examples.  It's fairly simple.  It took
a
> > > long time to return from the server.  I checked the cocoon comment at
> the
> > > bottom of the page - over 10 seconds.
> > >         The page returns the date and time, so is always changing.
> Subsequent
> > > calls are taking around 250-350 milliseconds.  I guess the cache is
> doing
> > > something, but that's still a fairly long time.  I didn't see any
> perfomance
> > > tweaking advice on the cocoon page.  Does anyone have some?
> >
> I must say have the same problems:
> 1- I can wait up to 10s to have my page whenever traffic is heavy
> 2- Cocoon seems to block when traffic becomes heavy !!!!!
>
> I dynamicaly generates list of elements that I layout as html tables. For
> example, I will produce, by extracting data from a database using XSP :
>
>
> <list-elt>
>  <elt> ... </elt>
> <elt> ... </elt>
> <elt> ... </elt>
> </list-elt>
>
> When I decided to deactivate Cocoon's page (see the cocoon.properties and
> turn on the NoCache object), I felt more comfortable! But, this is still
> slow.
>
> > First any server response time less than a second is respectable.
> > Second, the first access compiles the XSP page--thus the long compile.
> >
>
> Well, this is done at the first request. Nevertheless, is there a way to
> precompile all XSP pages ? Indeed, on-the-fly compilation is fine when
> developping, but in a production environment, this is a problem.
>
> > The simpler the logic, the simpler the stylesheet, the quicker the
> transform.
> > Of course, you could always throw more hardware at it.  The Cocoon2
> rearchitecture
> > addresses this very issue.  By moving from a costly DOM
environment--whose
> > real benefit is only seen on client side applications--Cocoon can
perform
> the
> > same transforms in half the time.
>
> I'm a Cocoon 1.7.4 (with some patches) user since I considered this
version
> as most stable version up to date. Am I wrong? How about Cocoon 2? I
cannot
> rely on a buggy version since my work is about to be on-line.
>
> >
> > There are some things you can do in the stylesheet level, check the
Xalan
> and
> > FOP projects for details.
> >
>
> I went to Xalan's FAQ page and they are talking about perfomance
> improvements in "What can I do to speed up transformations?" I noticed
they
> recommend to set the XSLTProcessor to function as a SAX DocumentHandler.
Is
> this possible with Cocoon? Are there limitations, ... ? How can I do that
> with Cocoon if so?
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
>