[ 
https://issues.apache.org/jira/browse/XALANC-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341381#comment-14341381
 ] 

Sergey Ushakov commented on XALANC-759:
---------------------------------------

Is it possible for you to attach 'ConvertCalendarsToPdp_1.xsl' here?

> Performance issue in XalanTransformer.transform()
> -------------------------------------------------
>
>                 Key: XALANC-759
>                 URL: https://issues.apache.org/jira/browse/XALANC-759
>             Project: XalanC
>          Issue Type: Bug
>          Components: XalanC
>    Affects Versions: 1.10
>         Environment: Windows
>            Reporter: Radhika MG
>            Assignee: Steven J. Hathaway
>            Priority: Critical
>
> We use Xalan 1.10 and Xerces 2.7 in our code built in C++ on Windows OS. 
> One of our customers who upgraded from previous version of our product to the 
> latest in suite is facing performance issue in Xalan transform. 
> Between two versions of our product, the Xalan and Xerces have been upgraded. 
> We tried to compare the time taken for transform with respective versions of 
> Xalan that we used in our products, for the same xml and style sheets. The 
> result is as below: 
> With Xalan 1.6 and Xerces 2.3
> Xalan -t -o pdp.out Calendar.xml ConvertCalendarsToPdp_1.xsl
> Source tree parsing time: 668.791 milliseconds.
> Stylesheet compilation time: 89.449 milliseconds.
> Transformation time: 324617.921 milliseconds. (5.41 minutes)
> With Xalan 1.10 and Xerces 2.7 
> Xalan -t -o pdp.out Calendar.xml ConvertCalendarsToPdp_1.xsl
> Source tree parsing time: 71.238 milliseconds.
> Stylesheet compilation time: 14.367 milliseconds.
> Transformation time: 3477100.2128 milliseconds. (57.95 minutes)
> Please suggest how we could improve the transform time. Does it require code 
> change at our end? 
> Please let us know. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to