[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

Re: [xsl] FOP : consumption memory

Subject: Re: [xsl] FOP : consumption memory
From: "Jean-Pierre Lamon jpl@xxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Sat, 16 Aug 2014 07:26:34 -0000

Thank you for your response Eliot.
I don't know if I can share these files, I must ask the principal because
it's a mandate.

The result is under :

I'll let you know

-----Message d'origine-----
De : Eliot Kimber ekimber@xxxxxxxxxxxx
Envoyi : vendredi 15 ao{t 2014 23:44
@ : xsl-list
Objet : Re: [xsl] FOP : consumption memory

If your content has natural page breaks (meaning elements that always
start a new page) you can always start a new page sequence at that point.

If your content does not have such nature page breaks then of course you
can't. In that case, one solution would be to generate the intermediate
area tree (a feature of FOP and all the other FO engines) and then use it
to find elements that happen to start on new pages and regenerate the FO
with page sequences started at those points. But that seems like rather a
lot of effort.

It might be easier to just give the Java VM running FOP more memory.

If this is XML that can be shared publicly I'd be interested in helping
diagnose this issue in exchange for the ability to use the XML for demos.



Eliot Kimber, Owner
Contrext, LLC

On 8/15/14, 1:32 PM, "Jean-Pierre Lamon jpl@xxxxxxxxxx"
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

>Thx Geert but I can't spread and break pages. It's a bibliography (swiss
>national library bibliography).
>If someone wants the XML and XSL to test, no problem :-) I'm not very
>professional with XSL, I maybe have done some horrors in my stylesheets
>my question is only : why FOP hangs and the little tool works perfectly.
>With absolute respect for people working for free tools like FOP.
>-----Message d'origine-----
>De : Geert Bormans geert@xxxxxxxxxxxxxxxxxxx
>Envoyi : vendredi 15 ao{t 2014 17:12
>@ : xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>Objet : Re: [xsl] FOP : consumption memory
>In my experience FOP does a poor thing with long page sequences.
>It seems to keep them in memory (for repagination maybe?) completely
>Memory footprint for FOP goes down dramatically
>if you have a logic that cuts the pages
>Rather than using mechanisms such as break before
>or similar, create new page sequences when you can
>(eg. per chapter, ...)
>That has helped me in the past
>At 16:33 15/08/2014, you wrote:
>>Hi All,
>>I know, difficult to say without having the
>>source, but could someone explain me why FOP
>>crashes, hangs (memory ?) for relative big
>>documents and a free small tool like XML2PDF
>>render the PDF perfectly and this, dramatically quicker compare to FOP.
>>Ive tried to play with JAVA memory etc no way.
>>Thanks and regards
>><http://www.mulberrytech.com/xsl/xsl-list>XSL-List info and archive
>>(<>by email)

Current Thread