From: Jeff Beal (email@example.com)
Date: Thu Feb 06 2003 - 06:39:47 PST
Just for the record, I'm building three books of over 1000 pages each (1300,
1500, and 1700 pages) using the PostScript backend. The size of the
resulting PS file is as high as 167 MB. XEP takes its time on these even
using -Xmx1000000000 (24, 31, and 22 minutes, respectively), but it does
seem to scale even to quite large and complex pieces of documentation. One
of the books is very graphic intensive, another has a lot of tables and
graphics. The third is mostly text, but still has a fair amount of
From: Kevin Ross [mailto:Kevin.Ross@iVerticalLeap.com]
Sent: Wednesday, February 05, 2003 9:00 PM
Subject: RE: [xep-support] Scalability?
So far, -Xmx228mb has solved my problem. Time is now < 55seconds (compared
to 4-9minutes), and memory only climbs to ~100mb.
What a difference!
These numbers are for:
512mb pc100 ram
[mailto:firstname.lastname@example.org] On Behalf Of Kevin Ross
Sent: Wednesday, February 05, 2003 7:11 PM
Subject: [xep-support] Scalability?
XEP churns for ~4 minutes (at about 80mb memory use), creating a pdf.
I have added the -Dcom.renderx.xep.VALIDATE=false. The result is a 0kb pdf
(sequence [master-reference delivery-sequence](flow [page-number 1]Exception
in thread "main" java.lang.OutOfMemoryError
I have an xsl, and xml that will reproduce this. Who wants it? The
resulting fo file (from the transformation) is ~1900kb.
If there is more recommended tuning, please let me know. I've just
introduced this into a production environment and we haven't made it through
the first day.
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to email@example.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
This archive was generated by hypermail 2.1.5 : Thu Feb 06 2003 - 06:34:27 PST