This one has got me scared...

I am in the process of working out an embedded (servlet) FOP solution for
some financial reporting.  The generated pdfs are probably around 20 pages..
does anyone have any info about memory requirements or problems I will run
into with multiple concurrent users?

will carter

-----Original Message-----
From: Savino, Matt C [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 30, 2002 4:01 PM
Subject: RE: Why is FO(P) a superior model than what most proprietary
tool s propose

We're using FOP in a production environment to render some management
reports and a very complicated lab report. We've had to limit the management
reports to about 2000 rows (~50 page PDF) because of FOP's memory issues
w/large PDFs. Also I worry about serious slowdown if we ever get 3 or 4
users on the same instance of the app server all running a decent sized PDF
at once. Does anyone know if wrapping FOP in a session bean would allow me
to distribute processing around to unused servers or otherwise handle the
java.lang.outOfMemoryError better? (We're on Weblogic 6.1)

I compared FOP to RenderX from XEP. RenderX was the only solution that
really mathces FOP's profile (XSL:FO based, java-based or at least platform
neutral, no extra servers to run or programs to install - if there are any
more out there, please post). For the report I was running, FOP was about 10
times faster than RenderX. But from most accounts performance between the
two should similar. I figure there must be something particular about my
stylesheet that RenderX didn't like. So I called XEP to see what kind of
support my interest in purchasing their $5k/cpu product might garner. They
weren't very helpful but did say they were insanely busy. I have a feeling
if you could come up with a high-performing commerical all Java FO->PDF
engine, you'd be very rich very quick.

Matt Savino


Reply via email to