[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
RE: Measuring performance
Subject: RE: Measuring performance From: Kay Michael <Michael.Kay@xxxxxxx> Date: Thu, 10 Aug 2000 13:55:36 +0100 |
> What is the ideal way to measure the performance of a specific bit > of XSL code? Are there any tools available for determining the > areas of your XSL code that are causing the heaviest loads on the > parser? Saxon now has a hook, the TraceListener, that could be used to plug in performance monitoring tools, but it would be rather laborious, and possibly not than effective, since Java only seems to measure time in milliseconds (I yearn for my old mainframe where I could get accurate counts of machine instructions executed) > Also, there are a few resources that indicate the efficiency > of using certain commands over others (ie using count instead of > xsl:number for certain applications). Is there any place that > provides a collection of these helpful suggestions? Not that I'm aware of. Usually, you'll get the right answer by assuming that the processor implements the algorithm given in the spec fairly literally, without optimisation. Any optimisations are likely to be very processor (and version) dependent - for example Saxon tries when it can to avoid n-squared performance when using an <xsl:number level="single"> instruction to number a sequence of nodes, but does it the hard way if there are any attributes such as count and from. Mike Kay XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: Measuring performance, Matthew Bentley | Thread | Text retrieval problem, Matthew Bentley |
RE: How dynamic is XSL?, Thorbjørn Ravn Ander | Date | RE: keys: repeated nodes from same , Kay Michael |
Month |
Keywords