| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Dynamic Q Creation Response Time |
« View previous topic :: View next topic » |
| Author |
Message
|
| Abishaik |
 Posted: Fri Jul 19, 2002 2:53 am Post subject: Dynamic Q Creation Response Time |
 |
|
Newbie
Joined: 22 Apr 2002
Posts: 4
Location: Japan
|
Hi Everybody!!!
I'm currently faced with an issue relating to response time. My current MQ architecture employed uses dynamic Q for receiving response from the Host System. The initial dynamic Q creation process (Call to Model Q) takes as much as 1.8~2.0 seconds. Whereas all the other processing including MQ Conn and the Host processing is taking about 0.5 seconds. The Dynamic Q is killing the response time very badly.
IBM documentations outline that we will have an impact by using dynamic Q but nothing as bad as the above. Does anybody know any specific parameters / tuning that can be carried out to mitigate the above situation. Any, ideas and inputs in this regard will be very very helpful.
Thanks in advance for your time,
Cheers
Abishaik. |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Fri Jul 19, 2002 3:16 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Are you using v5.1, if so upgrade v5.2 it speeds up Dynamic queue creation a great deal.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| dgolding |
| Posted: Fri Jul 19, 2002 5:15 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
What sort of response do you expect back from the host - how many messages are returned?
If you are only expecting one message back, think about rewriting your application for multiple requestors waiting on a single, permanent queue, doing a get with CORELL ID to get their (unique) response back. This is much more efficient. AFAIK this will also work for multiple-message response, even without using any grouping. You should be able to use the same corellation ID on multiple messages.
The corellation ID is the original message ID of the requestor. The reply server stuffs this into the corell. ID and sends it back to the Reply-to queue specified.
Just a thought, I read somewhere best practise says avoid using dynamic queues if performance is an issue...
HTH |
|
| Back to top |
|
|
| bigdavem |
| Posted: Sun Jul 21, 2002 5:54 pm Post subject: |
|
|
Acolyte
Joined: 16 Sep 2001
Posts: 69
Location: Sydney, Australia
|
| I agree. We started with a dynamic queue model but found it too sluggish so switched to a single queue matching on correl-ids. It sped it up 1000%. |
|
| Back to top |
|
|
| dgolding |
| Posted: Mon Jul 22, 2002 2:02 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
| One problem that can occur is that of "orphanned" reply messages. This is where the reply came back too late, for one reason or another, and the original requestor has timed-out and gone. To get round this, put a reasonable expiry time on your messages so they disappear every time somebody does a browse on the queue. |
|
| 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
|
|
|
|
