Subject: RE: [xsl] Saxon .Net API performance From: "Merrilees, David" <David.Merrilees@xxxxxxxxxxxx> Date: Wed, 1 Sep 2010 17:28:41 +0100 |
Thanks Andrew Some of our XSLT is unwieldy, and upgrading to XSLT 2.0 will help us organise our code more effectively. What will really help me sell this change to the people holding our purse strings is performance improvements. Apart from grouping, what features of XSLT 2.0 can I take advantage of to improve performance? Thanks David -----Original Message----- From: Andrew Welch [mailto:andrew.j.welch@xxxxxxxxx] Sent: 01 September 2010 07:55 To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: [xsl] Saxon .Net API performance > > I'm trying to show the performance difference we could achieve by moving to Saxon .Net API from Microsoft's XSLT 1.0 processor. Does anyone have any tips how I can get the best performance from the Saxon .Net API? > .. > > This is a confidential email. Tesco may monitor and record all emails. The views expressed in this email are those of the sender and not Tesco. > > Tesco Stores Limited I spent a few weeks at Tesco and the XSLT 1.0 stylesheets were pretty large and complex... the biggest benefit would simply be upgrading to XSLT 2.0. So perhaps rather than saying "I can get a nn% performance improvement" you could say "all of this complexity goes away" - complexity both in the stylesheets themselves and steps in the processing pipeline that would no longer be needed. -- Andrew Welch http://andrewjwelch.com
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Saxon .Net API performanc, Andrew Welch | Thread | Re: [xsl] Saxon .Net API performanc, Imsieke, Gerrit, le- |
Re: [xsl] Moving elements during id, David Carlisle | Date | RE: [xsl] Saxon .Net API performanc, Merrilees, David |
Month |