The only reason you'll start seeing major performance differences between XSLT and .NET is when you start having a really large volume of requests and at that point you really should be using caching of your macros anyway.
XSLT will start loosing performance when you are calling into .NET functions on a frequent basis.
.NET will start loosing performance when you are traversing large object graphs.
Xslt vs usercontrol macro..
I have read all the posts on when one should use one or the other, but none ascribe any performance stats.
Ie would doing the exact same in xslt as opposed to a usercontrol via the nodefactory have any performace hit?
The only reason you'll start seeing major performance differences between XSLT and .NET is when you start having a really large volume of requests and at that point you really should be using caching of your macros anyway.
XSLT will start loosing performance when you are calling into .NET functions on a frequent basis.
.NET will start loosing performance when you are traversing large object graphs.
I wrote a blog a few months back on choosing the right tool for the job: http://farmcode.org/post/2010/07/13/TheFARMe28099s-guide-to-Macros.aspx
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.