All registered XSLT extensions (either via the config or using the class attribute) are loaded in for every macro (that uses XSLT). You'' notice these in the trace information (marked with "umbracoXsltExtension"). I wouldn't worry too much about it, the performance cost of initialising the class objects is very small.
I do understand your point that if it's not being used in that XSLT, then why load it? The alternative is for the macro to parse the XSLT, check if it is being used, then load it (lazy loading) ... this would incur a bigger performance hit (due to the parsing).
All XSLT extensions are automatically loaded into new macros just in case you want to use them. There is a very, very slight performance penalty as each loads but as you can see from the trace it is extremely small.
Why is XSLTsearch Extension loaded with every xslt macro?
I use umbraco debug+trace mode to see what happen, and I noticed that XSLTsearch Extension will be loaded when each xslt macro be loaded.
I think this is not right, because I havn't used XSLTsearch with that page, so I needn't to load XSLTsearch Extension.
Hi sun,
All registered XSLT extensions (either via the config or using the class attribute) are loaded in for every macro (that uses XSLT). You'' notice these in the trace information (marked with "umbracoXsltExtension"). I wouldn't worry too much about it, the performance cost of initialising the class objects is very small.
I do understand your point that if it's not being used in that XSLT, then why load it? The alternative is for the macro to parse the XSLT, check if it is being used, then load it (lazy loading) ... this would incur a bigger performance hit (due to the parsing).
Cheers, Lee.
All XSLT extensions are automatically loaded into new macros just in case you want to use them. There is a very, very slight performance penalty as each loads but as you can see from the trace it is extremely small.
cheers,
doug.
is working on a reply...