[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Transformation time reporting problem with Saxon
On 3/14/06, Michael Kay <mike@xxxxxxxxxxxx> wrote: > > 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. Probably yes. But the the interesting new fact that we must be well aware of is that a transformation having a good deal of xsl:message instructions will run with different speeds, when run from the command line and from within another application. Cheers, Dimitre Novatchev
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|