On Jan 18, 2008, at 19:53, Dan F wrote:
Hi Dan,
At this point, I don't think I can trim my FO any further.
Initially, I had a
lot of embedded tables for layout which I've all changed to positioned
blocks. The rendering time went down considerably. I'm up to about
9-10
pages per second when generating PDFs. From what I read, this is
quite poor.
Can you give more context on the setup?
The biggest disadvantage where it comes to performance in your
approach (if that is what I think it is) is that the FO file is
ultimately stored on disk somewhere (unless you create and treat it
as a String or a Stream). So it generates more disk I/O, as the FO
first needs to be written then read back in.
If you would switch to using XML + XSLT, the FO document as such
would only exist in memory, as the SAX Events that result from the
XSLT transform. Less external I/O normally means more speed. As
Jeremias hinted, though, you would have to take care that the XSLT
code is written using best practices, or it may turn out to make
matters worse.
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
