Jebus wrote:
I have a fo that is about 21mb. If I keep throwing ram at fop I can get to run and it produces a 700 page pdf (3mb).
This is going to run in servlet environment with multiple users hitting this page, I don't think I can keep throwing ram it. Now granted this 700 page pdf is an extreme cause, but I will only need one and bunch of other users on at the same to to kill my system.
I don't have any images or forward references in my xsl. Some of the page-sequences turn into 20 pages in the pdf most are under 10, so that could be part of the problem. I don't see how I could make smaller page-sequences though.
Does anybody have any suggestions ?
Try to get rid of tables, or get the unreleased patch for the table memory leak from CVS. A 21MiB FO seems to be rather large for a 700 page result, think hard about simplifying the layout. Relying on inheritable properties and getting rid of unnecessary property settings may be a first step, although the effect is often insignificant. Look also for redundant nested blocks and redundant fo:inline and fo:wrapper elements.
J.Pietschmann
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
