Jignesh-NX01880 Kapadia wrote:
Hi ,
We are having here. We are using FOP here for our application it generates
a 81 page PDF in the output. It takes a very long time to generate it almost
more than 1 minute.
What sort of system are you running? how many CPUs, what o/s, (you mentioned memory below), and what version of FOP?
The figures you quote sound reasonsable for a basic single CPU system. I dont think you can do a lot to speed up processing time for a single document. Actually I found FOP to be one of the faster XSL-FO formatters around (mainly due to the fact that keeps and other difficult features are missing)
The user acceptance criteria is 15-20 seconds for such big PDF. if say more than 20 user try to generate the PDF file then we reach peak with our JVM and after that no user can do anything. We are using following FOP driver class.
org.w3c.dom.svg.SVGDocument.
I dont quite follow this bit. Are you saying you are creating SVG and XSL-FO in a DOM before presenting it to FOP for processing. This seems somewhat inefficient.
The websphere instance on which the application is running has 512MB of JVM size. We need that application can sustain a load of 60 user at a time to generate PDF document. The server has RAM of 3GB. The application is built with struts. Is there any way that FOP is can be made less memory intensive? so that it will not use much JVM but use CPU rather?
There have been some changes made to improve the memory consumption of tables, but these changes have not been included in any release of FOP. You will have to download the source from CVS maintenance branch and compile it yourself.
Chris
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
