Subject: RE: [xsl] XSLT use cases; data-centric to document-centrictransformations|
From: Peter Gerstbach <peter@xxxxxxxxxxxx>
Date: Tue, 8 Feb 2005 13:17:59 +0100
When comparing performance I found out, that xalan and saxon perform bad when there is only on big template. When the template is very large, saxon even ends up in an StackOverflowError.
I think you're drawing conclusions too hastily: "when" does not imply "because".
Saxon is unlikely to produce a StackOverflowError unless there is a very deep (usually infinite) recursion in your code, which I would have thought was more likely when you have many small templates than when you have one large one.
I admit, this example sounds weird and I should have explained it, when saying something about processors & performance. But my goal is to write a tool which creates stylesheets for very large fo documents, so I just want to find out, at which size XSLT processors begin to have problems.
What you are really saying is that you wrote a stylesheet that used a large template and it performed badly on two processors. The chances are that the inefficiencies in your code had nothing to do with the choice of XSLT processor, and nothing to do with the fact that it was using a large template. Rather, it was probably using an inefficient algorithm.