<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1"><font face="Helvetica, Arial, sans-serif">The biggest
memory consumer seems to be the process that compresses the PDF
document. I find that our document requires more than 3GB to process
with this option enabled and less than 1.5GB without it.<br>
<br>
Try the turning this option off in your xep.xml file as shown below:<br>
<br>
<!-- Backend options --><br>
<generator-options format="PDF"><br>
<!-- <option name="COMPRESS" value="false"/> --><br>
<!-- <option name="PDF_VERSION" value="1.3"/> --><br>
</generator-options><br>
<br>
By the way, I have a problem similar to yours. Our 2200 page book is
only one part of a larger catalog. Unfortunately, the other sections
contain references to products in the main section. I had posted some
messages here earlier to see if there is a way to write page numbers
and other data into the XEP log. I thought I would extract the data
with an editor and put it in a database, using it later to look up page
references for the other sections. I don't think this is possible, but
someone suggested looking at the XEP intermediate format. I have not
done this yet. If you look at it and can distill the information I
would like to know how to do it. If I try it first, I will post here.<br>
<br>
BJB<br>
</font></font><br>
Jost Klopfstein wrote:
<blockquote cite="mid013701c4c297$a8f36470$0602a8c0@Toshiba" type="cite">
<pre wrap="">Mike, Brian,
Thanks for your hints.
The document is in the 1000+ pages class with plenty of large SVG drawings
(>500 Kbytes).
I will check with my customer if I can drop the references between chapters.
If so, then I can use the split technology and build the TOC and Indexes
from the separate sections in XEP intermediate format.
Otherwise they have to buy a bigger server...
Does anyone know if there is an option to prevent XEP's in memory
processing?
Cheers, Jost
----- Original Message -----
From: "Mike Trotman" <a class="moz-txt-link-rfc2396E" href="mailto:mike.trotman@datalucid.com"><mike.trotman@datalucid.com></a>
To: <a class="moz-txt-link-rfc2396E" href="mailto:xep-support@renderx.com"><xep-support@renderx.com></a>
Sent: Friday, June 03, 2005 3:05 AM
Subject: Re: [xep-support] Splitting of large document
</pre>
<blockquote type="cite">
<pre wrap="">I have successfully processed 100mB+ documents of 1000+ pages - mainly
consisting of heavily formatted tables with 15 x 20 cells per page,
multiple pages per table, lots of data per cell, footnotes etc.
This included bookmarks and a simple Table Of Contents with internal
links to individual tables.
By placing each table / document chunk within a separate
<fo:page-sequence> I was able to keep the memory requirements very low
(not much more than the default).
I'm now also using XSLT pre-processing where I produce each
<fo:page-sequence> in a separate XSL-FO file and generate a master
processing document which sets up regions and page masters
and contains a list of the separate <fo:page-sequence> files to include.
I then process this master list with a simple XSLT to produce the final
FO for output to PDF.
I haven't used indexes (the TOC references etc. are constructed by the
XSLT) - so don't know what sort of overhead this produces.
Mike
Brian J. Butler wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I have also been working on a very large document (88MB FO file, 2200
pages of technical text and drawings). I can offer the following three
suggestions:
1. Make sure your Java -Xmx size is as large as possible. With
Windows this will be approximately -Xmx1600Mb.
2. Use the XEP flag to turn off PDF compression (in xep.xml or command
line). This will result in a very large PDF, but you can compress it
after rendering by opening it in Adobe Acrobat and then saving.
3. Switch to a 64-bit Solaris platform (Opteron processors). We
benchmarked one of these machines and found that we can -Xmx almost
unlimited memory. The speed is also very fast.
BJB
Jost Klopfstein wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
I ran into memory problems while rendering a large book with TOC,
indexes and references between sections.
I first thought I could just render section by section into XEP
intermediate format and then assemble the pieces with some custom
code into a large PDF using the PDF output generator.
However I will loose the TOC, indexes and the references between
sections.
Any ideas?
Thanks,
Jost
</pre>
</blockquote>
</blockquote>
<blockquote type="cite">
<pre wrap="">------------------------------------------------------------------------
</pre>
<blockquote type="cite">
<pre wrap="">Jost Klopfstein
*Axos Technologies Inc.*
OnDemand & Transactional Document Solutions, powered by XML
IT Consulting
*604 628-2248 Phone*
604-324-2380 Fax
jost (at) axostech.com
<a class="moz-txt-link-freetext" href="http://www.axostech.com">http://www.axostech.com</a>
</pre>
</blockquote>
<pre wrap="">
--
Brian J. Butler
BJB Software, Inc.
76 Bayberry Lane
Holliston, MA 01746
E-mail: <a class="moz-txt-link-abbreviated" href="mailto:bjbutler@bjbsoftware.com">bjbutler@bjbsoftware.com</a>
Web: <a class="moz-txt-link-freetext" href="http://www.bjbsoftware.com">http://www.bjbsoftware.com</a>
Phone: 508-429-1441
Fax: 419-710-1867
</pre>
</blockquote>
<pre wrap="">
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.322 / Virus Database: 267.5.2 - Release Date: 03/06/2005
Message Scanned by ClamAV on datalucid.com
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to <a class="moz-txt-link-abbreviated" href="mailto:majordomo@renderx.com">majordomo@renderx.com</a> from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service
</pre>
</blockquote>
<pre wrap=""><!----><a class="moz-txt-link-freetext" href="http://www.renderx.com/terms-of-service.html">http://www.renderx.com/terms-of-service.html</a>
</pre>
<blockquote type="cite">
<pre wrap="">
</pre>
</blockquote>
<pre wrap=""><!---->
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to <a class="moz-txt-link-abbreviated" href="mailto:majordomo@renderx.com">majordomo@renderx.com</a> from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service <a class="moz-txt-link-freetext" href="http://www.renderx.com/terms-of-service.html">http://www.renderx.com/terms-of-service.html</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Brian J. Butler
BJB Software, Inc.
76 Bayberry Lane
Holliston, MA 01746
E-mail: <a class="moz-txt-link-abbreviated" href="mailto:bjbutler@bjbsoftware.com">bjbutler@bjbsoftware.com</a>
Web: <a class="moz-txt-link-freetext" href="http://www.bjbsoftware.com">http://www.bjbsoftware.com</a>
Phone: 508-429-1441
Fax: 419-710-1867
</pre>
</body>
</html>