Off-line would be:  with fop.bat, generating static files.

The alternative is more expensive: write a cocoon serializer based on iText. But is that a guarantee for absolutely big performance? not sure. just a good guess. XSLT transformations may well defeat the purpose of using SAX, as they hold a lot of context in memory,

Maybe somebody out there has hands-on experience? Helloooo. Some good advice here?

Cheers,
Jos



On 11/15/2010 08:02 AM, Matthias Müller wrote:
Thanks for replying. We use Cocoon online to serve (<10) coworkers. What do you
mean with "off-line preparation"?
I heard about the good performance of iText. Since we do only xml processing i
need a way to apply xsl:fo stylesheet and afaik there is no xsl fo renderer for
iText.



Matthias



----- Ursprüngliche Mail ----
Von: Jos Snellings<[email protected]>
An: [email protected]
Gesendet: Freitag, den 12. November 2010, 14:45:20 Uhr
Betreff: Re: [C2.2] Fop Performance Issue with large documents

Hi Matthias,

Do you want to do that on line? Is off-line preparation a possibility?
As an alternative to FOP you could try iText which is completely
procedural if you want!

Jos

On 11/12/2010 11:16 AM, Matthias Müller wrote:
Hi there,
i ran into massive performance problems using Fop serializing large FO files
(PDFs with 500+ pages).

It takes up to 30 minutes for a single PDF and needs a lot of memory and cpu
power.
If i do the processing locally (no Cocoon but fop.bat), it takes about 2
minutes.
I know that FOP is not performant with large documents, but i only face that
when running inside Cocoon.

Is this a configuration issue?
Are there alternatives to FOP/Cocoon?
How do you process large xml based documents to pdf?
At the moment i still use Fop 0.20.5, what about the performance with Fop 1.0?

Matthias




---------------------------------------------------------------------
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]



---------------------------------------------------------------------
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]

Reply via email to