Thanks for your fast reply.

> Please check the following URL for ideas to improve the situation.
> http://xml.apache.org/fop/faq.html#OutOfMemoryException
Thanks, but we already did follow all this points. Memory usage is still
depending on the number of pages.

> This only works as long as pages can be fully resolved. As soon as you
> have a "page x of y" on each page the first page can only be output when
> the last page is known. Changing that to "page x" only can help solve
> this problem. Other references play into this as well.
Our pages contain no references at all. So theoretically a page can be
finalized after a new one has begun.

> The redesign contains some code that allows temporary serialization of
> pages until they are ready to be finalized.
What prevents a page from beeing finalized if there are no references in it?

> This will slow down the
> process but reduce memory usage. The problem is that a release from the
> redesign will still take a while so you're stuck with the above
> techniques to reduce memory usage until we have the redesign ready to
> take over.
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. Perhaps we can make some optimizations based
on our specific application.

Daniel




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to