Is there a way to approximate the memory footprint needed by Xalan to run an XSL?
For example, i am seeing that with SAX based transformation - using Xalan 2.7.0 and java 1.6_u13 with a bootclasspath option to force the JDK to load Xalan 2.7.0 - an input file of size 180 meg - and a simple XSL that does identity transformation (see below) The required memory footprint for heapsize is approximately 950Mb. -- my questions are: 1. is there a way to approximate the required memory footprint? 2. with SAX based processing, why does the 180Mb input file require such high overhead of heap memory? _____ XSL ____ <?xml version='1.0' encoding='UTF-8'?> <xsl:transform xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'> <xsl:template match="/"> <xsl:apply-templates select="*"/> </xsl:template> <xsl:template match="*"> <xsl:copy> <xsl:apply-templates select="@* | node()"/> </xsl:copy> </xsl:template> <xsl:template match="@*"> <xsl:copy> <xsl:apply-templates/> </xsl:copy> </xsl:template> </xsl:transform>
