|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Performance, Scalability Issue ? in non clustered env. |
« View previous topic :: View next topic » |
Author |
Message
|
objectthinker06 |
Posted: Wed Sep 19, 2007 10:46 am Post subject: Performance, Scalability Issue ? in non clustered env. |
|
|
Novice
Joined: 15 Aug 2006 Posts: 15
|
Here's the background on the environment before I ask for advise on the issue.
Background: We have a non clustered MQ environment and each server hosts one and only one Queue Manager and owns approx. 50 queues. All these queues are enabled for message persistence. The TCP connection to a queue manager is established using "inetd" daemon. The throughput for one Queue Manager in a day is approx. 5 million messages and is growing. And there are three queue's that are high volume and they contribute to 70% of the Queue Manager's total throughput per day. And the system activity on this machine is normal for example peak CPU is under 40% during peak traffic.
Issue: One of the high volume queues receives a total of approx. 2 million messages per day. Typically these messages arrive at a rate of 20K in 30 mins however sometimes we receive it at a faster rate i.e. 150K messages in 30 mins. And the messages are held in the queue for a few hours (6+ hours) before the consuming application completely de-queues it. While the application can be made to de-queue faster we can't do that because of downstream applications and infrastructure limitations.
So the question is: Does this queue holding so many messages approx. 500K messages at a time present any potential problems with regards to performance, scalability or availability ?
Thanks ! |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Sep 19, 2007 11:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
The messages on the queue illustrate a performance problem.
The receiving app should be scaled up to process them faster, so they don't pile up that high, deep, and for so long.
Otherwise, no. It's not a problem as long as the receiving app is only trying to get messages in FIFO order without using any selectors. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Wed Sep 19, 2007 2:59 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Ok to pile up....assuming the messages don't pile up so deep that the drive space available to the QM fills up at which point all bets are off for availability.
Also, get off of inetd and start using runmqlsr. Ever since MQ version 5.3 that has been the better way to go. Do a search here for reasons why. _________________ Peter Potkay
Keep Calm and MQ On |
|
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
|
|
|
|