I'm facing the same problem with XSL. We have to possibilities : 1- raw JSP reading a bean and creating javascript (wich dynamically update the content of the displayed document) 2- read the bean -> castor transformer -> xsl transformer to have a standard format -> xsl transform to transform this standard format to XHTML -> custom transformer that change XHTML into javascript string -> serializer
Résults : -the option number 2 is about 20 time longer than the number 1. -in option number 2, nearly 80% of the time is taken by the 2 XSL transformation -rewriting the stylesheet differently (they produce the same output, it's only a different implementation), transformation took from +50% to -30% time. -XSLTC gave something like -5% or -10% on the whole request (but this seem very few to me, maybe I made a mistake ?) Does anyone have a good URL about .XSL optimisation ? :) fabien. >-----Message d'origine----- >De: Matthew Langham [mailto:[EMAIL PROTECTED]] >Date: mardi 9 juillet 2002 13:48 >À: Cocoon-Dev@Xml. Apache. Org; Cocoon-Users@Xml. Apache. Org >Objet: FOP performance > > >Hi, > >we have a project where we are using Cocoon 2.0. We have a >simple pipeline >that generates a PDF document: > > <map:match pattern="print/pdfxyz"> > <map:generate type="webprintParameterPrint"/> > <map:transform type="webprintXYZ"/> > <map:transform src="webprint/contexts/XYZ/fragment.xsl"/> > <map:serialize type="fo2pdf"/> > </map:match> > >The XML data arrives as a request paramter (130 KB in size!) and the >stylesheet is 636 KB in size. We are using our own specific >generator and >transformer in the pipeline (but they don't do anything special). > >It takes 8.5 seconds to generate the PDF file - which is only >1 page! Quite >complex though with lots of tables etc - but no graphics. The >system is a >650 Mhz with 256 MB RAM. Our customer thinks that this is too >slow - and I >am looking for any ideas as to how we can improve the speed >(or perhaps this >is normal?). The duration is split evently between the >transformation step >and the FOP step. > >Would switching to 2.1-dev help? Why? >The stylesheet is very large - any idea here (translets?) >Perhaps it's quicker to use several stylesheets instead of 1 large one? >Is there a different PDF rendering engine we can use with Cocoon? >etc. > >Thanks. > >Matthew > >-- >Open Source Group Cocoon { Consulting, Training, Projects } >================================================================= >Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn >Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de >----------------------------------------------------------------- >Cocoon book: > http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20 >================================================================= > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
