Camel XSLT performance issue

[rchallapalli]

Hi,

I have a camel-jetty consumer for processing XML messages. Parallely carrying out performance tests. Before adding an XSLT transformation it gave me a throughput of  1286 & CPU shot up to 90..100%.. prior to adding XSLT processing it was around 2000.

No of concurrent users were 30 if I increase this the servicemix container goes out of memory. Average message processing time is absolutely fine. Below is my JMeter report. We are much much bothered about CPU utilization. Just adding one XSLT with average complexity, to transform one XML another, made a vast difference.

For my environment details & configuration  please see this link (

http://fusesource.com/forums/message.jspa?messageID=12643#12643) where I reported a performance prob with ActiveMQ. Its the same enviroment.

.............................WITH XSLT ..................WITHOUT-XSLT

Threads/users                            ................30                                          ............................30
                Loop counter                            ................1000...........................                                    1000
                Average.........................                                              21                                            .............................15
                Median..........................                                                 21..............................                                         15
                90% Line ......................                                          32                                            ..............................18
                MIN................................                                                              5 ...............................                                           2
                MAX                     ..............................93 ..............................                        96
                Throughput                                 ....................1286                                      ...........................1898
CPU                                    ..........................90-100% .........................<10%


           SMX: apache-servicemix-4.4.1-fuse-01-06/camel-blueprint
                Camel: Tried 2.8.1, 2.8.2, 2.9.0-RC1

Edited by: rchallapalli on Nov 18, 2011 2:17 PM

Edited by: rchallapalli on Nov 18, 2011 2:19 PM

[njiang]

What's your camel route looks like (with and without the XSLT) ?

[rchallapalli]

Hi n,

The route is very simple:

With XSLT

from(inputUri).routeId("inboundToCsfRequest")

.log("Consumed from ebxml inbound queue...")

.inOnly("xslt:input-to-output.xsl")   //?allowStAX=true")

.log("Transformed message..")

Without XSL:

from(inputUri).routeId("inboundToCsfRequest")

.log("Consumed from ebxml inbound queue...")

// .inOnly("xslt:input-to-output.xsl")   //?allowStAX=true")

.log("Transformed message..")

allowStAX=true gave me an exception so commented it...

thanks,

ravi

Edited by: rchallapalli on Nov 18, 2011 3:47 PM

[davsclaus]

XSLT does impact CPU performance, so it would be expected to be slower.

[davsclaus]

You can try upgrading the Saxon library. I think it may be faster in a newer release.