cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivelin Ivanov" <>
Subject Re: [FYI] Profiling Cocoon...
Date Sun, 06 Oct 2002 19:11:18 GMT

Thank you for the profiling, Stefano !
... and
Welcome Back to The Party !

----- Original Message -----
From: "Stefano Mazzocchi" <>
To: "Apache Cocoon" <>
Sent: Sunday, October 06, 2002 12:30 PM
Subject: [FYI] Profiling Cocoon...
> if you want to do something about it: he's working on Jerry, a
> super-light servlet engine based on native APR and targetted expecially
> for Apache 2.0)

A link to Jerry?

> 5) most of the time is spent on:
>    a) XSLT processing (and we knew that)
> 7) XSLTC *IS* blazingly fast compared to Xalan and is much less resource
> intensive.
> Discovery #3:
>   use XSLTC as much as possible!

Agreed. Sun's XSLTC team did a great job helping us to work through a lot of
bugs. XSLTC reached a stage that was good enough for many applications. At
least all the ones that I am using with Cocoon.
Therefore I made XSLTC the default engine. However there were reported
problems in some XSLT intense applications, and if I am not mistaken this
was the reason why XSLTC was switched out.

I absolutely agree with you that we should make XSLTC the default
transformer and continue working with Tom and the other XSLTC guys to fix
any outstanding bugs. It would be lovely if 2.1 ships with XSLTC.

I hope that Tom and Jacek are reading this message and will comment on the
current status of XSLTC and how it compares to Gregor now.

I think that XSLTC, Caching and the sitemap Expire attribute will make 2.1 a
very decent container for scalable applications.
BTW, do we have a document on the "expire" attribute already?

> NOTE: our current root sitemap.xmap indicates that XSLTC is default XSLT
> engine for Cocoon 2.1, but the fact is that the XSLTC factory is
> commented out, resulting in running Xalan. We should either remove that
> comment or uncomment the XSLTC factory.
> I vote for making XSLTC default even if this generates a few bug reports.


> Anyway, Cocoon is pretty optimized for what we could see. So let's be
> happy about it.



To unsubscribe, e-mail:
For additional commands, email:

View raw message