Joerg, Keiron, et al,
This is why I have harped on the theme of lookahead. The layout design
simply must accommodate it, and must be able to preserve as much
information as possible from the initial layout attempts to minimise the
work of subsequent attempts. I have, as I have said before,
On Fri, 2002-08-09 at 19:06, J.Pietschmann wrote:
As for the redesigned code, FOs appear to refer to layout
managers, which in turn refer to areas. Unless it is somewhere
ensured that either areas are properly removed from managers
and/or managers are removed from the FO, the possible early
McKenzie/CanWest/IBM@IBMCA
cc:
Subject: RE: FOP memory usage
Thank you, Lloyd.
Of course, I do have sections, and I would not mind to make a page sequence
break after each of them. If it were a 300-page document, I would even be
willing to make more files out of it, like in a FrameMaker® multi-file
a separate sequence. If not, I'm
afraid I don't have the expertise to help :-(.
Lloyd
Matthias Fischer [EMAIL PROTECTED] on 11/22/2001 09:20:04 AM
To: [EMAIL PROTECTED]
cc: Lloyd McKenzie/CanWest/IBM@IBMCA
Subject: RE: FOP memory usage
While waiting for an answer that would, once again, help me
Hi,
If you want to help improve the memory usage in a future version of fop I
suggest you follow the current cvs developments. This will attempt to
address this issue along with a number of other issues.
As far as memory is concerned the ideas area:
- have the smallest set of variables and
files.
Regards,
Mike
-Original Message-
From: Maring, Steve [mailto:[EMAIL PROTECTED]]
Sent: 9. november 2001 15:29
To: FOP dev list (E-mail)
Subject: FOP memory usage
I'm using fop-0.20.1.
I started with a 650KB XML file that I transformed into a 4MB XSL:FO file.
Running this file
: Maring, Steve [mailto:[EMAIL PROTECTED]]
Sent: 9. november 2001 15:29
To: FOP dev list (E-mail)
Subject: FOP memory usage
I'm using fop-0.20.1.
I started with a 650KB XML file that I transformed into a 4MB XSL:FO file.
Running this file through FOP to generate a PDF used about 90MB of memory
An: [EMAIL PROTECTED]
Betreff: Re: FOP memory usage
I also had this problem.
To render a fo to pdf (around 100 pages) allocated more then 150 MB.
When I got rid of references (in my case page-number-citations) the
allocated memory was just 40 MB.
Regards,
Jens
Michail Bikoulis wrote:
You
respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: FOP memory usage
Make sure you're using -hotspot. Try setting the initial and max heap
size to 256M if you have it. Turn on verbose garbage collection to see
what's happening. Even though it says 'No garbage collection
Media, Inc.
Phone:(301)897-7722
-Original Message-
From: David Neumann [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 09, 2001 1:57 PM
To: [EMAIL PROTECTED]
Subject: Re: FOP memory usage
Indeed, thanks to a recommendation from Mr. Lillywhite to use a
sequence for each of my pages
On Tue, 03 Jul 2001 16:42:47 Rorvick, Chris wrote:
I mean O(C) where C is a constant amount of memory.
That may be the case for the pdf generation but when FOP needs to deal with
reading an xml document, resolving properties, creating an area tree then
rendering to the target (which may be
On Mon, 02 Jul 2001 20:13:14 Rorvick, Chris wrote:
After a few days of using FOP and thumbing through the PDF spec, I've
made
the following observations. It seems that PDFs should be able to be
generated in constant memory, but FOP currently does not work this way.
Are
both of these
12 matches
Mail list logo
