Subject: RE: [xsl] Transformation time reporting problem with Saxon (Was: Re: [xsl] A new Sudoku xslt implementation (Was: Re: [xsl] Sudoku - A solution in XSLT 2)) From: "Michael Kay" <mike@xxxxxxxxxxxx> Date: Mon, 13 Mar 2006 22:36:44 -0000 |
> So, the problem is that when run from the command line Saxon does not > include the time for xsl:message instructions in the time it reports > when the -t option is specified. However, if Saxon is invoked by > another application (the XSelerator in my case), although the same > command-line string is used for the invocation, the time reported by > Saxon includes the time for the xsl:message instructions. That's an interesting theory, but I don't think it's true. I think a more plausible conjecture is that the performance of xsl:message depends strongly on the message destination, and that it's the choice of message destination that actually affects the result. Michael Kay http://www.saxonica.com/
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Transformation time reporting, Dimitre Novatchev | Thread | Re: [xsl] Transformation time repor, Dimitre Novatchev |
Re: [xsl] Obscuring static content , G. Ken Holman | Date | [xsl] New Table when I hit the nth , Phil Jenkins |
Month |