Daniel Tschan wrote:
Thanks, but we already did follow all this points. Memory usage is still
depending on the number of pages.
The FO tree will not be reclaimed until a page sequence ands.
Also some structures managing PDF data will grow steadily.
On the other hand less memory usage can result in increased speed. Can you
give us some hints so that we can try to find a quick and dirty solution
for now? The reasons that prevent the pages from beeing finalized at once
may not apply in all cases.
The area tree for a page can eat up quite a bit of memory,
depending on the complexity of the layout. Tables are the
worst problem in this respect, especially table spanning
pages. Just in case, images also block memory indefinitely.
Other infamous memory leaks are caused by basic-links.
If you really want to strip memory usage to the bone:
- don't use images
- don't use user fonts
- don't use internal links
- don't use page number citations
- don't use borders
- don't nest block FOs deeper than 2-3 levels
- factor out common property settings and rely on inheritance
- don't use hyphenation
- don't mix blocks and text at the same level
- don't use tables
- don't use footnotes
- don't use markers
- don't use fancy static content
- don't use small-caps
- don't use text decoration
Yes, this takes most of the fun away, but if you have so
little memory that even 30 pages are a problem, you'll have
to take drastic measures.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
