[I'll give J. a
breather on this one] Assuming you've made certain that the bottleneck is in FOP
and not your XSLT transformation, the only thing you can really do to help with
very large reports is to break the PDFs into multiple page-sequences. IE start a
new page-sequence every X nodes. If you have natural page break that you can
use, no one will ever notice in the final output. Otherwise you may have awkward
page breaks in your document. I have attached an XSLT stylesheet that we use to
essentially break the XSL:FO into "chunks". Every 10 Investigator (=doctor)
nodes we start a new page-sequence. Since this report has a page break for
each new investigator anyway, the end result is no
different.
We increased our
max PDF size on this report from 30 pages to 200 using this method, and
seriously sped up rendering time for large reports. FYI - we are
running Weblogic on HP-UX with -hotspot, max-heap-size=512MB. For some
reason, the Wintel JVM seems to perform a lot better than HP-UX on FOP, and in
general.
Hope this
helps,
Matt
|
pvh_XmlToFo.xsl
Description: pvh_XmlToFo.xsl
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]