Hello, I am using Xalan C++ 1.9.0 on MCVC6.0 and have fairly poor performance. I am using the .lib file that is in the Windows distribution on the Apache site. I am using Xalan from within a standard Win32 DLL, in a fairly large stand-alone application.
I am using Xerces 2.6.0 to build the XML, and then using Xalan to load the XML from a file, and compile it before performing the XSL transform. Performance in DEBUG build is 30mins for a 1.5MB XML. In RELEASE it is about 10 mins for the same 1.5MB XML file. Performance in the command line samples (XalanTransform and XalanTransformerCallBack) is much better (less than 3 mins). I used the same code in my DLL - so could it be a memory problem ? I have tried various approaches: -checked that key() and other xsl features listed at http://xml.apache.org/xalan-c/usagepatterns.html are not being used. -using a callback to write out the data (don't think this helps - the performance problem occurs where about 512 bytes of data are written out, then processing, then at the end a steady write out) -compiling XML source and XSL stylesheets before performing the transform. >From the call stack it looks like Xalan is NOT using Xerces. However, one approach I have not tried is to rebuild Xalan so that it does not depend on Xerces. So, two questions: -Any idea how to remove Xalan's dependency on Xerces, and would this improve performance? -Any idea of Xalan 1_10_0 has better performance ? (I see some memory bug fixes...) ___________ Sean Ryan
