Simon, Thanks very much for your note on checking for the use of '//' in the xpath values. I was using this for my Row selection. When I changed the stylesheet to use a fully qualified /Results/Row specification instead of //Row, the overall transformation time was reduced from 415725 ms (almost 7 minutes) to 12921 ms (13 seconds). Wow.
Alan > -----Original Message----- > From: S Woodside [mailto:[EMAIL PROTECTED] > Sent: Monday, July 07, 2003 7:54 PM > To: Alan Edel > Cc: [EMAIL PROTECTED] > Subject: Re: AxKit performance problem > > > Can you post the code in question? It's hard to say without seeing it. > > One common performance hit is using // in an xpath - that can be really > slow. > > simon > > On Monday, July 7, 2003, at 05:58 PM, Alan Edel wrote: > > > xsltproc does take the same amount of time to process the > > transformation, and the stats show that on a 4000 entry > > xml file, each of my "Row" entries takes one-tenth of a > > second to process. This accounts for the 6-minute > > transformation time I'm seeing. > > > > Now I have to figure out why each row is taking so long... > > I am doing an xsl sort on a numeric value, and each row > > displays several columns each of which is formatted with > > a call-template function. > > > > At this point, I'm going to limit the amount of data > > returned and leave it at that. > > > > Thanks for the tips, > > > > Alan > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
