Changing XSLT Version to Improve Latency

In a customer use case, slower performance was observed in terms of latency, when the XSLT source version for Mapper activity was 1.0 as compared to 2.0. The project is configured to read from an XML file, which is parsed by the Parse XML activity and the output content is further processed by the Mapper activity, as shown in the following image:

The XSLT source for 'Mapper activity was set to the default 1.0 version as shown in the following image. This version can be configured as follows: Select Activity > Input Tab > Right-click on the mapping element (RHS) > Select Show Edit Tab -> Select XSLT Source.

Testing and Measurement

The testing was focused on the aspect below:
  • The tests were run to measure end to latency with XSLT version set to 1.0 and then with 2.0.

Solution for Performance Improvement

It was observed that the latency improved considerably by 100% when the version was changed to 2.0 from 1.0.