Tuesday 27 January 2009

ESB XSLT versus XQuery performance

The search results returned by search service of Adapt CRM are enclosed in CDATA section inside SOAP response. The search results xml is tightly coupled to the underlying database as tag names are derived from database columns and table names.




Part 1


STAX api based transformation used to transform bond format xml to more eligible xml








Part 2

XQuery based transformation inside the bus used to transform bond format xml to more eligible xml









Results
Both test produced very close results, STAX based transformation was faster by few milliseconds on average when processing 100 entity records per request. 10 threads used to load test for 60 seconds


---------

Interesting ESB benchmarking by oracle:

http://www.oracle.com/technology/products/integration/esb/files/oracleesb10-1-3performanceguide.pdf



1 comment:

anon_anon said...

you may want to look at vtd-xml, the latest and most advanced xml processing api that is a must have for high perfomrance ESB

vtd-xml