We are about to run a 38,000 page book through the PE.
Has anyone done a book that big before?
Anyone have a clue as to hardware requirements? RAM? Pagespace settings? Have a guess as to how long it will take?
John T. Jarrett
BAE Systems | Arbortext version 5.4 | LOGSA XSL-FO v 1.5
Another data point to consider: using XSL-FO our team found that documents in excess of 2000 pages sometimes took 6 or more hours to render. This was using PE 5.2 on Solaris 9 with Adobe Distiller server, stylesheets did some generated text. Source consisted mainly of text, CALS tables, and on average a graphic every 3 pages; note however that results varied considerably from document to document, there was no clear way to predict what exactly affected composition times. Java virtual memory was an issue as John mentioned. The sluggishness prompted us to switch to FOSI.
Project Manager, Knowledge Services Information Technology
Certified Lean Six Sigma Green Belt
Telephone +1 613 763 4873 / ESN 393 4873
Well, we can't get our 38,00 pager to run full through.
This is the current error message:
<data name="errorMessage" value="com.arbortext.e3.E3RequestError:" subprocess=" terminated=" unexpectedly=" while=" executing=" the=" composition=" operation."="/>
<data name="outputCode" value="500"/">
This is only slightly better than getting the "General XPath error."
In order to keep it from timing out (with Susan Fort's help - thanks!) I've set the subprocess pool as follows:
<subprocesspool default="yes" id="pool-default" maxsubprocesses="2" maxbusyinterval="0"<br"/>minSubprocesses="1" maxLifetime="0">
Quad core server, 4 GB RAM, 14 GB page file (the standard 2 min/4 max GB setting was not enough). Crashes after about 4 hours.
I tried without the appendices to cut down on gentext - no change.
I'm saving the temp files and they all appear to be complete - x2.xml as well as the intermediate and the outputdir with ati tags. The x2 is 40 GB and the intermediate/ouputdir file is 450 GB <-- can't even open it with Arbortext. I was hoping they were crashing and I could tell where, but each has an ending </production> or </fo:root> tag as appropriate.
Other than rqbody.dat (which apparently I don't know how to open), I've looked at all the transaction files and find no help at all.
We just did a test on a book that is half that size (still in the huge department) and are back to the General XPath Error even though our contractor has published it in the past with 5.3 and the older LOGSA v1.4 stylesheets (which has badly formed jumbled up tables).
Any ideas on what to try next? At 4 hours to a crash, this is turning into a really long process.
John T. Jarrett
BAE Systems | Arbortext version 5.4 | LOGSA XSL-FO v 1.6