Subject: Re: [xsl] GByte Transforms From: Jeff Kenton <jeffrey.kenton@xxxxxxxxxxx> Date: Wed, 02 Jun 2004 16:40:05 -0400 |
The quest then is to find ways of writing stylesheets for these types of transform that give predictable performance results. It would be ideal for a processor to handle this without any fuss but turning an arbitary stylesheet into one that executes in linear time will never be viable for XSLT. Some of our more practical ideas we have been kicking around are: -
Ignore the problem, leave to stylesheet writer testing.
Extra smarts in the compiler to warn of the use of potentially non-linear behaviour. E.G. Recursive templates not being tail recursive, nested loop/
template constructions.
As above but aided by structural information for better targeting.
As above but with automatic re-writing where possible.
Optional runtime monitoring for non-linear behaviours, perhaps as an addition to profile information.
Runtime stop limits, E.G. if predicted execution (as monitored by the runtime) time exceeds a limit terminate.
Non-linear algorithm replacement with linear but slower algorithms, applies to both runtime and compiler.
Subset XSLT to limit the scope for non-linear transforms.
And perhaps the most controversial, don't provide this support for XSLT but only XQuery where predictability should be better.
------------------------------------------------------------------------- = Jeff Kenton Consulting and software development = = http://home.comcast.net/~jeffrey.kenton = -------------------------------------------------------------------------
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] GByte Transforms, Kevin Jones | Thread | Re: [xsl] GByte Transforms, Kevin Jones |
encoding shift_jis into an attribut, Matthew Simoneau | Date | Re: [xsl] using a pdf file as backg, Glen Mazza |
Month |