Hello Jeremias,

thank you for the Answer. Regarding your question, no I dont serialize the 
Value Object to a file. We make from our VO�s an XML (String Object) and after 
that transform it with XSLT. You can see the percentage value is very low. I 
don�t think, that the reason is here. About the half time is spent in FOP, and 
I dont know if I can optimize here something. See the attached p�ece of the 
result from OPTIMIZEIT (Borland). I think should take my focus the procedures 
that take long.

Thanks in advance,

Jan

54.56% - 72726 ms - org.apache.fop.fo.pagination.PageSequence.makePage()
26.83% - 35770 ms - 
org.apache.fop.fo.pagination.PageSequence.formatStaticContent()
26.83% - 35770 ms - 
org.apache.fop.fo.pagination.PageSequence.layoutStaticContent()
26.83% - 35770 ms - org.apache.fop.fo.flow.StaticContent.layout()
26.83% - 35770 ms - org.apache.fop.fo.flow.Block.layout()
25.86% - 34468 ms - org.apache.fop.fo.flow.Block.layout()
24.75% - 32989 ms - org.apache.fop.fo.flow.Table.layout()
22.38% - 29837 ms - org.apache.fop.fo.flow.AbstractTableBody.layout()
19.86% - 26481 ms - org.apache.fop.fo.flow.TableRow.layout()
18.8% - 25065 ms - org.apache.fop.fo.flow.TableCell.layout()
16.18% - 21574 ms - org.apache.fop.fo.flow.Block.layout()
5.29% - 7063 ms - org.apache.fop.fo.PropertyList.get()
2.5% - 3341 ms - org.apache.fop.fo.PropertyManager.getBorderAndPadding()
2.38% - 3185 ms - org.apache.fop.fo.FOText.layout()
2.25% - 2999 ms - org.apache.fop.fo.PropertyManager.getHyphenationProps()
1.29% - 1724 ms - org.apache.fop.fo.PropertyManager.getFontState()
0.82% - 1097 ms - org.apache.fop.fo.flow.ExternalGraphic.layout()
0.25% - 337 ms - org.apache.fop.fo.flow.PageNumber.layout()
0.23% - 318 ms - org.apache.fop.fo.flow.PageNumberCitation.layout()
0.17% - 234 ms - org.apache.fop.fo.PropertyManager.getMarginProps()
0.16% - 223 ms - org.apache.fop.layout.BlockArea.start()
0.15% - 204 ms - org.apache.fop.fo.PropertyManager.getBackgroundProps()
0.12% - 172 ms - org.apache.fop.layout.BlockArea.<init>()
0.12% - 163 ms - org.apache.fop.fo.PropertyManager.getAccessibilityProps()
0.07% - 103 ms - org.apache.fop.fo.PropertyManager.checkBreakBefore()
0.07% - 100 ms - org.apache.fop.layout.BlockArea.end()
0.06% - 82 ms - org.apache.fop.fo.PropertyManager.checkBreakAfter()
0.04% - 58 ms - org.apache.fop.layout.Area.addLineagePair()
0.0% - 12 ms - org.apache.fop.fo.PropertyManager.getAuralProps()
0.0% - 11 ms - org.apache.fop.layout.Area.addChild()
0.0% - 10 ms - org.apache.fop.layout.Area.getAbsoluteHeight()
0.0% - 10 ms - org.apache.fop.layout.Area.isFirst()
0.0% - 6 ms - org.apache.fop.layout.Area.spaceLeft()
0.0% - 6 ms - org.apache.fop.layout.Area.getHeight()
0.0% - 6 ms - org.apache.fop.fo.FObjMixed.layout()
0.0% - 6 ms - org.apache.fop.layout.Area.getFontInfo()
0.0% - 6 ms - org.apache.fop.fo.PropertyManager.getRelativePositionProps()
0.0% - 5 ms - org.apache.fop.datatypes.IDReferences.createID()



-----Urspr�ngliche Nachricht-----
Von:    Jeremias Maerki [SMTP:[EMAIL PROTECTED]
Gesendet am:    Freitag, 7. M�rz 2003 18:26
An:     [EMAIL PROTECTED]
Betreff:        Re: performance FO

Hello Jan,

please search in the mailing list archives for "performance". There have
been several threads in the past around this topic. I'm sure you'll find
interesting stuff there.

On 07.03.2003 17:59:09 Zmitko, Jan wrote:
> how can I optimize the Performance in FOP. I�m using the 0.20.5 version. I
> have measured the time of generating PDF with the tool Profiler of Borland.
> It�s very interesting to see how many time the classes/componets of FOP
> require to generate a PDF. I�ll attached the issue.
>
> Can me anybody help or give some tipps how to generate my Stylesheet to
> optimize the workflow. The different Stylesheet I use, are attached to this
> mail, too.

Another comment to something I saw in your mail:

> 1.64% - 2194 ms - xml.VOToXMLEncoder.writeObject()
> 0.18% - 247 ms - java.io.FileOutputStream.<init>()

Are you serializing the value objects to files before running them
through XSLT and FOP? If yes, try to generate SAX events from your value
objects and pipe them directly through to the XSLT process. If you
serialize your XML, the XSLT engine has to parse it it again. That takes
time. See http://xml.apache.org/fop/embedding.html (the examples at the
bottom) for ideas.

Good luck!

Jeremias Maerki


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

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

Reply via email to