I have a sinking feeling another xalan/xerces combination is somewhere in
my classpath.
The problem? I don't have a classpath env. variable set.
I wonder where that list of places the 1.4JVM looks for classes on
win32 is?
On Thu, 14 Mar 2002, Peter Jacobs wrote:
> Strange, the difference was ve
Strange, the difference was very noticeable, in the XSL-transforms (to
HTML,Excel,FO) as well as in de FOP-PDF generation step.
Like XML->FO->PDF in 10 seconds instead of 50!!
Other people reported the same thing
e.g. see the thread "Re: FOP performance on Win98/JRE 1.3.1" on FOP-DEV.
> That's in
That's interesting that it made a difference for you. On our XML/XSL, it
didn't make much difference - maybe it shaved 1-2 seconds of a 60 second
rendering.
-David
On Wed, 13 Mar 2002, Peter Jacobs wrote:
>
> Are you using the included Xalan and Xerces.jar? I replaced them with Xalan
> 2.2 and X
Actually the FAQ (at http://www.owal.co.uk/cgi-bin/fopfaq.cgi since I have
given up on the interactive Jyve program)
doesn't contain much on memory consumption. I will add in the "new page
sequence" when I (or someone else) comes up with an example.
Alex
At 20:22 12/03/2002, Chuck Paussa wrote:
Are you using the included Xalan and Xerces.jar? I replaced them with Xalan
2.2 and Xerces 1.4.2 and got big improvement in speed (on Win2000 and Sun
Solaris).
Peter
Peter Jacobs
Freelance multimedia programmeur
De Budetstraat 8
B-3201 Aarschot
[EMAIL PROTECTED]
016/5732
I've been making pretty big PDFs with a similar system and can share a few
off-the-cuff comments.
It's obvious to me that the structure of your fo document - sequences,
page layout, flows, etc - can make a significant difference in memory
usage and speed. However, I don't have enough concrete conc
Here's our benchmarking ballpark numbers:
On an average report (~30 rows/page, ~7 cols., ~7 chars/column, no new
page-sequences possible), output on Weblogic--I see around 500ms/page
running on on my PIII-933 NT4, 512MB ram, max heap-size=256MB. I see about
900 ms/page on our RISC 2X550Mhz HP-UX
David,
Most likely you're running out of memory. You should set a new
page-sequence every once in a while (~60 lines of report would make it
every page) Look on the FAQ about memory consumption
Chuck
David Le Strat wrote:
All,
I am currently working on a project where we are dynamically creating
