Hi Abel,
Thank you for your reply. Sorry, I copied/pasted my last email sent to
the other mailing list and forgot to be more specific.
Yes, I did log the time as follow:
> long time1 = System.currentTimeMillis();
> transformer.transform(src, res);
> long time2 = System.currentTimeMillis();
And the difference between time2 and time1 is really about 40 seconds.
In command line, I redo the same test with the same XML and it takes
only 5 seconds.
I will try to increase the memory allocated to my apps server though
to see if there's a significant improvement and I'll let you know.
However, can the performance be affected if I have a XSL file that
includes many others XSL files when it is being used in a servlet, for
instance:
[...]
<xsl:include href="../template1.xsl" />
<xsl:include href="template2.xsl"/>
<xsl:include href="template3.xsl" />
<xsl:include href="template4.xsl" />
<xsl:include href="template5.xsl" />
[...]
<!-- Body -->
<fo:flow flow-name="xsl-region-body">
fo:block>
<xsl:call-template name="template1" /> <!--in template1.xsl-->
<xsl:call-template name="template2" /> <!--in template2.xsl-->
<xsl:call-template name="template3" /> <!--in template3.xsl-->
<xsl:call-template name="template4" /> <!--in template4.xsl-->
<xsl:call-template name="template5" /> <!--in template5.xsl-->
</fo:block>
</fo:flow>
[...]
Thanks again for your help,
Thomas
-----Original Message-----
From: Abel Braaksma [mailto:[EMAIL PROTECTED]
Sent: Monday, March 12, 2007 12:05 PM
To: [email protected]
Subject: Re: Performance issue XSL:FO
Thomas Yip wrote:
> 4> transformer.transform(src, res);
>
> However line#4 seems to be taking a lot of time to execute (around
40
> seconds).
Thomas, good to see you here. But it would be much easier for us to
help
you if you at least answered my questions that I raised in the
original
thread on the xsl-list, especially to those that are a member of both
lists (and many are). Also, if your statement "seems to be" is changed
in "is", add a little code snippet that on itself illustrates the
problem.
And I like to repeat my experience with FOP 0.93 here: I use it from a
servlet with no performance hit whatsoever, but both memory consuming
of
FOP and in-memory serialization of the HTTP output stream can be
causing
this. But first and foremost: add time logging statements to make sure
your statement above holds.
Cheers,
-- Abel Braaksma
---------------------------------------------------------------------
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]
