Erwin wrote: > On Tue, 16 Apr 2002, Lajos Moczar wrote: > > > In my experience, it is memory that is the key factor. Running with > > 512MB allocated to the JVM, I can produce 53 pages of PDF, but no more. > > I would have thought that SAX-based processing would allow you to > > process as much as you want, but obviously there is something with PDF > > documents that eliminates this advantage. > > > > Regards, > > > > Lajos > > galatea.com > > > I am able to produce a PDF of +/- 250 pages with 256MB of heapsize, but > with no forward references. It is in fact FOP (in my experience) that uses > so much memory and that forms a barrier. > > IIUC FOP has a Java object for almost everything on a page (if you have a > paragraph on a page that contains some inline elements, this is > encapsulated in a hierarchy of Java objects). Once a page is completely > created and every reference is resolved, it is converted into its PDF > equivalent, and the Java objects can be destroyed. > > If you have a lot of forward references (e.g. for page numbers in a Table > Of Contents) it can take up a lot of memory, before everything is > resolved. Therefore, I am not using a Table Of Contents at the moment. > > I am not sure if this is completely clear, but this is my experience.
This is also my experience. I'm working on the same project as Erwin and I've also enlarged my heapsize. It is now set at 256MB minimum. I'm still able to generate a table of contents for the document although it takes some time before the whole document (263 pages) is generated. Greetings, Carolien -- http://carolien.ulyssis.org http://htmlwedstrijd.ulyssis.org --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
