Author |
Message
|
prasunad |
Posted: Fri Oct 17, 2014 3:18 am Post subject: WMB v8 Throughput/Performace |
|
|
Novice
Joined: 10 Jul 2014 Posts: 22
|
Hi Guys,
Can you please guide me to the performace reports of using various WMB Nodes.
1) Compute
2) XSLT
3) Mapping
4) Java
Thanks |
|
Back to top |
|
 |
McueMart |
Posted: Fri Oct 17, 2014 3:51 am Post subject: |
|
|
 Chevalier
Joined: 29 Nov 2011 Posts: 490 Location: UK...somewhere
|
|
Back to top |
|
 |
smdavies99 |
Posted: Fri Oct 17, 2014 4:40 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Please do not use those short url's. I know of several corporate firewalls where 'bit.ly' (and others) are blocked. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
Vitor |
Posted: Fri Oct 17, 2014 5:05 am Post subject: Re: WMB v8 Throughput/Performace |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
prasunad wrote: |
Can you please guide me to the performace reports of using various WMB Nodes.
1) Compute
2) XSLT
3) Mapping
4) Java |
IMHO any such reports are nearly valueless if they even exist. Certainly for ESQL & Java the performance of the nodes is directly tied to the skill of the developer as you can write badly perfoming code in either.
I'd sooner select the node I use based on the kind of transformation that's needed, and the skill set of the developers; i.e. if you have a predominently Java shop with good Java people then it's pointless trying to get them to learn ESQL or XSLT. _________________ Honesty is the best policy.
Insanity is the best defence.
Last edited by Vitor on Fri Oct 17, 2014 6:23 am; edited 1 time in total |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Oct 17, 2014 5:14 am Post subject: Re: WMB v8 Throughput/Performace |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Vitor wrote: |
I'd sooner select the node I use based on the kind of transformation that's needed, and the skill set of the developers; i.e. if you have a predominently Java shop with good Java people then it's pointless trying to get them to learn Java or XSLT. |
Not quite. You have to get them to learn ESQL and XSLT the broker way. However the learning curve will be a lot less steep.
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
McueMart |
Posted: Fri Oct 17, 2014 6:45 am Post subject: |
|
|
 Chevalier
Joined: 29 Nov 2011 Posts: 490 Location: UK...somewhere
|
|
Back to top |
|
 |
prasunad |
Posted: Mon Oct 20, 2014 12:11 am Post subject: |
|
|
Novice
Joined: 10 Jul 2014 Posts: 22
|
Thanks Guys.
Do agree the dev standards would be diff for a beginner and expert.
But was looking to see which is more peformant.
esp ESQL, Mapping Node, XSLT, Java all doing similar processing. |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Oct 20, 2014 1:16 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
prasunad wrote: |
Thanks Guys.
Do agree the dev standards would be diff for a beginner and expert.
But was looking to see which is more peformant.
esp ESQL, Mapping Node, XSLT, Java all doing similar processing. |
The answer is probably not XSLT which really gets up the nose of some Java devs I know (if the transformation is complex. simples ones may be faster but I tend to avoid XSLT if at all possible). _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
kimbert |
Posted: Mon Oct 20, 2014 10:49 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Your question is not really answerable. Which language is 'best' depends on how you ( or the organisation that you work for ) define 'best'. Raw speed is hardly ever the most important issue - regardless of what some may tell you.
Getting the design correct is almost always the biggest factor that affects performance. _________________ Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
Back to top |
|
 |
prasunad |
Posted: Tue Oct 21, 2014 6:26 am Post subject: |
|
|
Novice
Joined: 10 Jul 2014 Posts: 22
|
From the IBM Report.
V8 introduces a new Mapping node which allows the user to visually map
and transform data from source to target. This new mapping node has
excellent performance characteristics, and is a viable option for
performance sensitive transformations. Some tests have been measured
performing close to optimised programmatic transformations in ESQL,
Java and .Net, with the typical measurement being 50%. Existing maps
developed prior to V8 will continue to work as-is, but will be opened as
read-only within the WebSphere Message Broker Toolkit. At the time of
writing this report, automatic migration of existing maps is not possible.
Trying to understand the statement..
Some tests have been measured
performing close to optimised programmatic transformations in ESQL,
Java and .Net, with the typical measurement being 50%.
does this mean the mapping node is 50% performant when compared to ESQL. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Oct 21, 2014 7:06 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
prasunad wrote: |
does this mean the mapping node is 50% performant when compared to ESQL. |
No, it means that a fully optimized map is 50% performant to a fully optimized piece of ESQL. A badly written / optimized map will be less performant than that. A map trying to perform a complex transformation will be still less performant that a piece of ESQL that only needs 2 lines.
prasunad wrote: |
Trying to understand the statement |
The correct translation of the IBM-speak:
Quote: |
This new mapping node has
excellent performance characteristics, and is a viable option for
performance sensitive transformations |
is
Quote: |
The new mapping node doesn't suck like the one in v6 & v7, and you can now consider it for performance sensitve transformations when in v6 & v7 you just ruled it out of those use cases because it sucked so badly |
_________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
prasunad |
Posted: Wed Oct 22, 2014 6:17 am Post subject: |
|
|
Novice
Joined: 10 Jul 2014 Posts: 22
|
Makes Sense...
Thanks Vitor for the explanation...  |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Oct 22, 2014 6:21 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Actually, the GDM should run on par with ESQL or Java. That performance report is out of date, if I recall correctly. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Oct 22, 2014 6:42 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqjeff wrote: |
Actually, the GDM should run on par with ESQL or Java. That performance report is out of date, if I recall correctly. |
So to expand:
Quote: |
The new mapping node doesn't suck like the one in v6 & v7, and you can now consider it for performance sensitve transformations on a par with ESQL & Java, when in v6 & v7 you just ruled it out of those use cases because it sucked so badly. |
_________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Wed Oct 22, 2014 9:47 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Vitor wrote: |
mqjeff wrote: |
Actually, the GDM should run on par with ESQL or Java. That performance report is out of date, if I recall correctly. |
So to expand:
Quote: |
The new mapping node doesn't suck like the one in v6 & v7, and you can now consider it for performance sensitve transformations on a par with ESQL & Java, when in v6 & v7 you just ruled it out of those use cases because it sucked so badly. |
|
You missed your calling as a Copy Editor for Technical Journals. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
|