You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by Thorbjørn Ravn Andersen <no...@c.dk> on 2004/05/26 10:32:11 UTC
Re: spending too much time in PropertyList.findProperty
Steven McNeel wrote:
> (2) org.apache.fop.fo.PropertyList.findProperty -> 26.4%
>
> - this is the other main culprit. The time spent here is
> divided fairly evenly among the following three methods of
> PropertyListBuilder:
>
> computeProperty -> 8.8%
> isCorrespondingForced -> 5.7%
> getShorthand -> 5.8%
Similar numbers are found with OptimizeIt (6.21%, 7.9%, 7.78%
respectively) with JDK 1.4.1 under Windows with FOP 0.20.5. Those three
were the top 3 hotspots.
It also appears that I have CPU and memory problems with FOP due to too
complex tables.
--
Thorbjoern Ravn Andersen "...plus...Tubular Bells!"
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: spending too much time in PropertyList.findProperty
Posted by Thorbjørn Ravn Andersen <no...@c.dk>.
Chris Bowditch wrote:
> The changes to Table performance dont apply to AWT Renderer mainly
> because AWT Rendering uses very different code to the main part of
> FOP's layout/rendering engine, which is geared up for PDF, Postscript
> and other print formats.
Now I have done a quick test of this on our server with a large print.
With 0.20.5 I end up with a footprint after FOP has run of 120 Mb, which
falls to 20 Mb, and with the latest CVS I end up with 96 Mb which also
falls to 20 Mb. I
Thank you for letting me know. The saving is enough to make a difference.
>> By accident I first checked with the code in HEAD, which did not work
>> well, so I am convinced that 1.0 is still some time away :)
>
>
> Could you elaborate on what isnt working? One of my current goals is
> to get the development version working to a similar level as 0.20.5.
I just ran the sample FO file described above through. No tables showed
up, and a lot of text was put on top of each other in a single place.
This was AWT only. Feel free to download and try.
--
Thorbjoern Ravn Andersen "...plus...Tubular Bells!"
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: spending too much time in PropertyList.findProperty
Posted by Chris Bowditch <bo...@hotmail.com>.
Thorbjørn Ravn Andersen wrote:
> I have now made a comparison between 0.20.5 and the latest maintainance
> code in CVS, and I do not see the effects described above. I have
> tested with the sample AWT-previewer in FOP, and found that the memory
> footprint are very similar, but I will now check in the actual
> environment. Do I need to provide some configuration parameters which
> may change the behaviour of FOP?
The changes to Table performance dont apply to AWT Renderer mainly because AWT
Rendering uses very different code to the main part of FOP's layout/rendering
engine, which is geared up for PDF, Postscript and other print formats.
<snip/>
> By accident I first checked with the code in HEAD, which did not work
> well, so I am convinced that 1.0 is still some time away :)
Could you elaborate on what isnt working? One of my current goals is to get
the development version working to a similar level as 0.20.5.
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: spending too much time in PropertyList.findProperty
Posted by Thorbjørn Ravn Andersen <no...@c.dk>.
J.Pietschmann wrote:
> I suspect this is be cause row and cell areas are referenced
> from their corresponding FOs itself and are therefore kept
> in memory together with all their descendants until the page
> sequence is completely rendered (in contrast to all other
> area objects which are reclaimed after a page is rendered).
> There is a fix for this in CVS.
I have now made a comparison between 0.20.5 and the latest maintainance
code in CVS, and I do not see the effects described above. I have
tested with the sample AWT-previewer in FOP, and found that the memory
footprint are very similar, but I will now check in the actual
environment. Do I need to provide some configuration parameters which
may change the behaviour of FOP?
To clarify what I currently need to render, I would have attached a
sample FO-file but this is not accepted on the list. Interested parties
may have a look at http://unixsnedkeren.dk/fop/t2.zip. Suggestions are
appreciated. We are considering redesigning this to avoid using tables
so much, but if better performance can be achieved with what we have,
that would be nice. Basically the JVM in which this runs, has a very
large heap and little CPU to spare, and spends much too much time
garbage collecting, as well as take quite a while in rendering.
By accident I first checked with the code in HEAD, which did not work
well, so I am convinced that 1.0 is still some time away :)
--
Thorbjoern Ravn Andersen "...plus...Tubular Bells!"
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: spending too much time in PropertyList.findProperty
Posted by "J.Pietschmann" <j3...@yahoo.de>.
Thorbjørn Ravn Andersen wrote:
> It also appears that I have CPU and memory problems with FOP due to too
> complex tables.
>
I suspect this is be cause row and cell areas are referenced
from their corresponding FOs itself and are therefore kept
in memory together with all their descendants until the page
sequence is completely rendered (in contrast to all other
area objects which are reclaimed after a page is rendered).
There is a fix for this in CVS.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org