I am not using any forward references.

I've debugged memory allocation and 
noticed that FOP allocates about 700Kb of memory
for each page processed. This remains allocated to the
end of pagesequence.

If I've understood right, it's AreaTree that grows bigger and bigger.

Is there any way or is it possible with current design to implement
explicit clearing of already handled/rendered objects/pages from AreaTree
to enable GC to collect objects that are needed no more?

I am intrested for donating work for FOP
to make possible processing very long pagesequences.

Aki



-----Original Message-----
From: Keiron Liddle [mailto:[EMAIL PROTECTED]]
Sent: 16. joulukuuta 2002 16:12
To: FOP
Subject: Re: FOP and AreaTree serialization


On Mon, 2002-12-16 at 14:32, Salonen, Aki wrote:
> Hi!
> 
> I've been using FOP for Inventory reporting in PDF format.
> It works great with documents less that 200 pages when
> we have enough memory in server.
> 
> We need to produce reports with pages up to 1000 pages
> and within one pagesequence.
> 
> I would like to serialize AreaTree to filesystem
> to prevent server running out of memory.
> 
> What is best place to start from?
> I've notice that sources in CVS have AreaTree subclasses:
> 
> AreaTree.AreaTreeModel 
> AreaTree.RenderPagesModel 
> AreaTree.StorePagesModel 
> 
> Does these classes already provide support for areatree
> to-filesystem-caching
> during pagesequence rendering?

Yes this is implemented, the CachedRenderPagesModel does it.
Caching only really helps when there are forward references. All other
pages are rendered and streamed out straight away.


> How about latest 0.20.5rc release. Didn't find those classes there.

It is not implemented in the releases, this functionality is only in the
development in cvs.

Your help with the development would be appreciated.

> Any help appreciated.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to