Author |
Message
|
bprasana |
Posted: Mon Apr 18, 2011 5:02 pm Post subject: Is there any known performance issue with XSLT node in WMB 6 |
|
|
 Disciple
Joined: 18 Apr 2005 Posts: 179
|
Hey guys,
Have you experienced any performance issue in WMB6.0 for XSLT transformation.
All i am doing is sending a message 800KB message to XSLT node. I am not doing any transformation. But it consistently takes 2- 4 seconds.
Any suggestions?
i know WMB6 is going out of support, but we are only migrating end of this year to production. till then we have to live with this lag.
This is all i have in the XSL file.
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
</xsl:template>
</xsl:styplesheet>
here are the timings from the trace nodes
1.7 MB 3.3 s
1 MB 2.2 s
766 KB 0.2 s |
|
Back to top |
|
 |
Gaya3 |
Posted: Wed Apr 20, 2011 1:41 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
quite not sure....but will get more idea..if you could raise a PMR _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Apr 20, 2011 1:43 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Except that the PMR process is not designed for handling performance issues in general.
Nor will bprasana be able to open a PMR on v6.0 if bprasana waits more than two weeks. |
|
Back to top |
|
 |
bprasana |
Posted: Wed Apr 20, 2011 6:08 am Post subject: |
|
|
 Disciple
Joined: 18 Apr 2005 Posts: 179
|
Actually, I just tries with 6.1. That has the same issue too!
Let me try to raise PMR. If not for performance I could atleast ask for some bench marking results I think.
Thanks for the replies. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Apr 20, 2011 6:14 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
bprasana wrote: |
Actually, I just tries with 6.1. That has the same issue too!
Let me try to raise PMR. If not for performance I could atleast ask for some bench marking results I think.
Thanks for the replies. |
You can certainly ask.
But the PMR process does not cover performance issues.
The Performance Report SupportPacs provide a lot of benchmarks. |
|
Back to top |
|
 |
paintpot |
Posted: Wed Apr 20, 2011 7:29 am Post subject: Re: Is there any known performance issue with XSLT node in W |
|
|
Centurion
Joined: 19 Sep 2005 Posts: 112 Location: UK
|
bprasana wrote: |
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
</xsl:template>
</xsl:styplesheet>
|
I presume that's a typo!
Have you tried running this standalone, i.e. not in a node and not in WMB? Might be interesting |
|
Back to top |
|
 |
bprasana |
Posted: Wed Apr 20, 2011 8:32 am Post subject: |
|
|
 Disciple
Joined: 18 Apr 2005 Posts: 179
|
Sorry, yes that was a typo. I wasnt able to copy from remote machine so i typed that whole thing
You mean through some other parser? - I have not tried it. Do you recommend any? |
|
Back to top |
|
 |
paintpot |
Posted: Thu Apr 21, 2011 2:43 am Post subject: |
|
|
Centurion
Joined: 19 Sep 2005 Posts: 112 Location: UK
|
bprasana wrote: |
You mean through some other parser? - I have not tried it. Do you recommend any? |
Various Transform classes in java, e.g. XMLUnit's
org.custommonkey.xmlunit.Transform
You could run it outside WMB, and then in a java node for the fun of it!  |
|
Back to top |
|
 |
bprasana |
Posted: Tue Apr 26, 2011 3:21 pm Post subject: |
|
|
 Disciple
Joined: 18 Apr 2005 Posts: 179
|
I tried this in RAD which comes with default XSLT parser. Only the first one took more time subsequent transformations took no more than a second. |
|
Back to top |
|
 |
rbicheno |
Posted: Tue Apr 26, 2011 11:23 pm Post subject: |
|
|
Apprentice
Joined: 07 Jul 2009 Posts: 43
|
What other nodes are in your flow and what method are you using to time/measure performance?
I have run hundreds of performance tests on XSLT node on v6 and v6.1 and to my knowledge there is no performance issue. Sounds to me like you have trace and/or debug enabled on your flow or execution group. I would suggest you check these. Measuring performance of the flow with trace nodes in and enabled is also no advisable.
For a sanity check try running the xslt sample from the samples gallery, the input message is included, this is the same benchmark flow used in the performance reports so we know its sound. This will help validate your environment. If you want a tool to drive the flow to measure performance then look here:
http://www.alphaworks.ibm.com/tech/perfharness
Hope that helps |
|
Back to top |
|
 |
bprasana |
Posted: Thu Apr 28, 2011 6:07 pm Post subject: |
|
|
 Disciple
Joined: 18 Apr 2005 Posts: 179
|
Hi,
It did not help much. Also the CPU utilization of that EG is varies from 50- 75% in topas.
I loaded about 1K messages using the tool you send above using mqjava.Sender.
I did not understand the output. But i checked the time taken by looking at the increase in msg count. it still is about 2-3s for a that simple transformation.
I also checked the EG for any trace or debug, there is nothing set on it at the moment.
Do you have any suggestions?
Thanks
bprasana |
|
Back to top |
|
 |
|