Hi all,
I tested FOP-0.94, FOP-0.95beta and FOP-0.20.5 using pdfoutline.fo. I added
more fo:block(simple text) to the pdfoutline.fo file until the size of this
file is reached 7.74M. Both FOP-0.94 and FOP-0.95beta require at least 896M
heap size to run and produce 1580 pages PDF document.
On May 12, 2008, at 16:37, LN wrote:
Hi
I tested FOP-0.94, FOP-0.95beta and FOP-0.20.5 using pdfoutline.fo.
I added
more fo:block(simple text) to the pdfoutline.fo file until the size
of this
file is reached 7.74M. Both FOP-0.94 and FOP-0.95beta require at
least 896M
heap size to run
Jean-François El Fouly a écrit :
So I hired the team member who's competent in profiler usage next week
but I must say at the moment I'm still stuck :-(
The sysadmins made a tarball from the staging server and copied
everything to a similar server that has full profiling instrumentation
Andreas,
I added multiple fo:blocks, each fo:block contains the same text (Exact
text: Rather than performing transformation with an XSLT before invoking
FOP, it is possible, if you use XT as your XSLT engine, to just call FOP and
have it call XT for you. To do this, run the class
On May 12, 2008, at 16:57, LN wrote:
snip /
All these fo:blocks are in the same page-sequence.
That explains a lot. This is a known scalability issue. FOP has
problems with very large page-sequences, as it is currently based on
a total-fit approach for the entire page-sequence. If you
