| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Performance issue MQOUTPUT node. |
« View previous topic :: View next topic » |
| Author |
Message
|
| Charlie |
 Posted: Wed Oct 13, 2004 2:17 am Post subject: Performance issue MQOUTPUT node. |
 |
|
Newbie
Joined: 12 Oct 2004
Posts: 5
Location: Johannesburg S.A
|
Hi All
I’m having a problem with response in the MQOUTPUT node.
We are using a CWF format message of 810k, when I do the MQOUTPUT (using destination list) the put takes 2 seconds. Is there any way of getting this faster?
I have tried changing the format of the message to BLOB, but the transform takes 2 seconds although the PUT runs thru faster.
We are running WMQI V2.1.
Thx
Liberty Life
_________________
Thx
Charles Kapp
Liberty Life
IT Consaltant |
|
| Back to top |
|
 |
| kirani |
| Posted: Wed Oct 13, 2004 8:41 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
How do you know the PUT (MQOutput) takes 2 sec to write the message on the output queue? How are you measuring this?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| JLRowe |
| Posted: Wed Oct 13, 2004 11:13 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
Charlie,
Are you changing the input message in any way?
If the message is changed then the broker has to parse and then serialize the message, this is probably causing your performance problem. The 'just in time' parser is designed to optimise simple routing message flows that do not manipulate the message, in these cases the input bitstream is passed straight through to output.
Of course, if you have to change the message then the only thing you can do is read the performance support packs and try to optimise your code in some way. |
|
| Back to top |
|
|
| Charlie |
| Posted: Wed Oct 13, 2004 10:57 pm Post subject: |
|
|
Newbie
Joined: 12 Oct 2004
Posts: 5
Location: Johannesburg S.A
|
Hi All,
Thanks for the response. 
The problem here is that we do manipulate the incoming message. We create a whole new output from two inputs.
The way I measured the times is by putting a trace node in front and after the MQOUTPUT node.
_________________
Thx
Charles Kapp
Liberty Life
IT Consaltant |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Oct 14, 2004 8:35 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Your total time also includes the time for writing the Trace files. Another way of finding the time would be to enable the message flow trace and then look at Timings before and after MQOutput node.
Also, can you write a small MQ app to do a MQPUT on the same queue and see if it's taking the same time. If it's taking the same time then it's MQ problem (you need a faster disk).
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
