| Author |
Message
|
| ramesh.govindaswamy |
 Posted: Fri Nov 11, 2005 2:40 am Post subject: IBM MQ - Performance Tuning |
 |
|
Apprentice
Joined: 25 Oct 2005
Posts: 42
|
We have configured a persistent queue and tried to pump the 200000 messages using multi threaded program on Sun solaris box with MQ version 5.3.
The performance we got was around 6000 messages per minutes which is very slow.
When we changed the queue property to non-persistent, we were able pump 200000 messages in a minute.
I would like to know the parameters that can be tuned to get the same performance when the queue is persistent.
Thanks in advance. |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Fri Nov 11, 2005 2:46 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
this is not a matter of parameter setting and tuning. no lunch is for free, and so is persistence of messages. if you want to have persistent messages, you have to pay the price.
persistent messages are written to the log, they are "hardended" and will not get lost e.g. at queuemanager restart. make your i/o as fast as possible.
you will never get the same performance for persistent messages as you get for non persistent messages.
you may check the supportpac site for performance reports.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri Nov 11, 2005 3:07 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
If your application allows it, you can get a improvement by "batching" the processing of messages. For example, get 10 messages under syncpoint and then commit all 10 messages at once.
Also, putting your log filesystem (/var/mqm/log) on its own high speed device can help.
_________________
-wayne |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Nov 11, 2005 3:43 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Persistent message throughput is usually limited by the I/O performance of the disks.
Use "Fast Write" cached disks, make sure the SAN or RAID array is set up properly.
Make sure the MQ queue manager has exclusive use of the disks, separate logs from queues and so on. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Nov 11, 2005 3:56 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
|
| Back to top |
|
|
| hopsala |
| Posted: Sat Nov 12, 2005 6:29 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
|
| Back to top |
|
|
|
|
