On 16 Oct 2013, at 12:08, Jesper Tverskov wrote:
Hi Michael
I'm not sure that I understand your answer.
When I make my XSLT+FO transformation at the command line:
MSXML+Antenna House = 1.3s
Saxon 9n + Antenna House = 5s
Saxon 9j + Antenna House = 2.5s
The above figures are a little hard to understand considering that the
XSLT step only takes a fraction of the FO step. Somehow AH must be
optimized to use MSXML at the command line. I don't know if it is
possible to overwin the "Java VM startup" problem as long as I have to
use the command line interface of AH?
I'm afraid I know nothing about AntennaHouse or what facilities it provides for
invoking different XSLT processors. However, a startup cost of 2.5s for
starting up a Java VM doesn't surprise me in the slightest. I'm slightly more
surprised by the 5s for .NET, since I was under the impression .NET startup
costs were lower than Java.
Are you sure they are invoking MSXML via a command line interface? I would
think it's more likely they are invoking it directly via an API call, in which
case it will be much faster than any processor invoked using via a command line
exec.
Michael Kay
Saxonica
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--