>In this case you have requested whitespace (line breaks and indentation) >around the value-of's result. This means XSLT has to create the >concatenated data. I'm not sure how Xalan-C s handling that, but in Xalan-J >you might also be creating a Result Tree Fragment to contain the result of >that computation (if so, that's an opportunity for optimization). Either >way, there is going to be some additional heap churn. > >As an experiment, you might want to try eliminating the whitespace: > > <xsl:with-param name="arg1"><xsl:value-of select="substring >(.,2)"/></xsl:with-param> > >and see whether Xalan-C is clever enough to recognize this as equivalent to >the first version. Nope. The memory stay growing. I'm a little bit confused about the memory growing all the time during the transformation. If I use "<xsl:value-of..." and this is a Result Tree Fragment, Xalan-C should free the Fragment as the "<xsl:call-template" returns, because no one can access the Fragment.
HolgeR -- holger floerke d o c t r o n i c email [EMAIL PROTECTED] information publishing + retrieval phone +49 2222 9292 90 http://www.doctronic.de
