Thank you all for the suggestions. Here is what I have done so far, maybe this could help others with projects that they are working on. I ran a 1000 TRANSACTION element version of the detrpt1.xml through two different XSLT processors, both from the command line, so I could get an understanding of the XSL transformation time, taking fop out of the equation.
The two XSLT processors Xalan-j - version 2_7_0 - Processing time - 2 min 10 seconds Saxon - version 8 - Processing time - 2.5 seconds I was surprised to see such a huge difference in performance, but I believe I performed the benchmarks correctly, I was just creating a text file for the test, but each created a text file of the same size, with all the data from the xml present. So now I am plugging Saxon in to the actual application and I will see what I get. I will repost to the mail list, if anything that might be helpful to others comes up. Again, thanks for all the help. Danny Gallagher The Gainer Group 6525 The Corners Parkway Suite 215 Norcross Ga, 30092 -----Original Message----- From: Andreas L Delmelle [mailto:[EMAIL PROTECTED] Sent: Thursday, November 10, 2005 3:16 PM To: fop-users@xmlgraphics.apache.org Subject: Re: Large PDF - Performance On Nov 10, 2005, at 21:10, J.Pietschmann wrote: > Andreas L Delmelle wrote: >>> Oh, you might want to look into pre-compiled stylesheets, too. Saxon >>> supports those. I don't know about Xalan. >> It does: see http://xml.apache.org/xalan-j/xsltc_usage.html > > Well, XSLTC compiles XSLT into Java. Compiled style sheets are usually > a bit less drastic, it just means the style sheet is kept in a > javax.xml.transform.Templates object. Sorry, my mistake. > This saves parsing the XML into an internal data structure and > static optimizations. > Standard Xalan supports compiled style sheets in the latter sense too. > Not that XSLTC is actually a completely separate code base and has > quite a bit more problems than standard Xalan. Yep. Still Sun has adopted it and made it part of Java 1.5. If the stylesheet can be compiled into Java w.o. problems, it is noticeably quite a bit faster (for all but the first run, evidently). Cheers, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
