Feedback
Did this article resolve your question/issue?

   

Article

Slow performance when using DOM and the XML Converters

Information

 
TitleSlow performance when using DOM and the XML Converters
URL Nameslow-performance-when-using-dom-and-the-xml-converters
Article Number000188189
EnvironmentProduct: XML Converters
Version: 6.2
O/S: All Supported
Database: N/A
Application: N/A
Question/Problem Description
When using DOM files as part of the conversion process, performance is found to be slow.
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
DOM is known to have poor performance.
Resolution
Avoid using DOM. 

if the app is using Saxon, it's worth considering using Saxon’s TinyTree model. The Saxon DocumentBuilder returns an XdmNode instead of a Document. 

According to the Saxon documentation (http://www.saxonica.com/html/documentation/sourcedocs/thirdparty.html):

“Transforming a DOM can take up to 10 times longer than transforming the equivalent TinyTree.” 

If using Saxon, it is possible to persist any static XML as PTree documents to vastly improve loading time. http://www.saxonica.com/html/documentation/sourcedocs/ptree.html 

It is also possible to precompile XSLT documents - http://www.saxonica.com/html/documentation/using-xsl/compiling.html 
Workaround
Notes
Last Modified Date5/18/2017 6:30 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.