I think maintainability should sell by itself, by virtue of cost savings
for bug fixes, changes, or new features. Maybe a future XSLT2 solution
won't live up to the promises of XY% performance gain, so I think you
shouldn't even try to sell on this argument but rather try to direct
their attention towards cost savings by maintainability. Of course you
should try to quantify the possible savings. Take, for example, the last
10 change requests and their outcome in terms of man-hours spent and
bugs newly induced. Or the quota of rejected change requests due to
estimated costs or lack of predictability. Then quote the experts --
Andrew, Dr Kay, etc. -- saying something like "XSLT2 increases
maintainability by YZ%, lowering maintenance costs by the same amount".
Of course management will object that these gains are only achievable if
the people in charge of maintaining the solution are experiences XSLT2
developers. So you have to offset training costs from the prospective
gains. And maybe you'll have to hire an expert for some days (depending
on complexity) to help you redesign the application.
For immediate performance gains, you should use a profiler (will saxon
-TP cope with XSLT1 stylesheets? it should) and then consider using
xsl:key or other adequate measures on the bottlenecks. But these are
rather speculative or general thoughts, given that the only time I spent
at Tesco's was when I bought something there in England or Prague.
Gerrit
On 01.09.2010 18:28, Merrilees, David wrote:
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(_dot_)j(_dot_)welch(_at_)gmail(_dot_)com]
Sent: 01 September 2010 07:55
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
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
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--
Gerrit Imsieke
Geschäftsführer / Managing Director
le-tex publishing services GmbH
Weissenfelser Str. 84, 04229 Leipzig, Germany
Phone +49 341 355356 110, Fax +49 341 355356 510
gerrit(_dot_)imsieke(_at_)le-tex(_dot_)de, http://www.le-tex.de
Registergericht / Commercial Register: Amtsgericht Leipzig
Registernummer / Registration Number: HRB 24930
Geschäftsführer: Gerrit Imsieke, Svea Jelonek,
Thomas Schmidt, Dr. Reinhard Vöckler
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--