ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General Discussion » potential MQ performance issue

Post new topic  Reply to topic
 potential MQ performance issue « View previous topic :: View next topic » 
Author Message
lozaza
PostPosted: Wed Oct 16, 2013 4:43 pm    Post subject: potential MQ performance issue Reply with quote

Apprentice

Joined: 04 Mar 2013
Posts: 27

We have MQ installed on three App Servers with exactly same configurations(including versions, queues and clusters) and talking to three MainFrame queue managers.

there are alias queues on App servers pointing to local queues on Mainframes straight away.

Request traffics(Messages) are supposed to go into three app server nodes 'equally'(or at least at similar rate) by F5 but now according to Tivoli Omegamon channel performance, only 30 messages are going from
App Servers node 1(compared to 250 throu node 2 and 235 throu node 3) to mainframe. it is relatively very slow. For my understanding F5 doesn't load balance MQ and MQ is getting requests from the server. We gonna do another test to put messages straight to MQ on node 1 soon to see if it is still slow but is there anything else I could check to make sure it might not be an MQ issue.

things we have done so far:
restart queue manager on node 1 also restart the server, around 2% CPU usage.
Health check done on MQ including all the channels are running, alias queues can see the destination.
as three nodes are all VM, we VMotioned three nodes onto the same host
Network team confirm the connections are good
restart F5

Thanks guys,
JS
Back to top
View user's profile Send private message
hughson
PostPosted: Thu Oct 17, 2013 1:04 am    Post subject: Reply with quote

Padawan

Joined: 09 May 2013
Posts: 1916
Location: Bay of Plenty, New Zealand

F5 is a connection balancer not a message balancer.

Each time a new connection is made F5 has the chance to choose where to send it.

If there are not exactly the same number of messages going over each connection from the time it is connected to the time it ends, you will definitely see a skew. Also of course if the number of connections is not exactly divisible by 3 you will have a skew. In fact, getting any such scenario to *EXACTLY* share out the messages is actually extremely difficult.

Anyway - you have told us the numbers of messages you are seeing going to each mainframe queue, can you also tell us something about the connections and how many F5 chooses to send to each?

Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
lozaza
PostPosted: Thu Oct 17, 2013 10:39 pm    Post subject: That is what we are going to find out Reply with quote

Apprentice

Joined: 04 Mar 2013
Posts: 27

Thanks a lot hughson,

not sure if it is the best idea, we might stop the channels between the app server and mainframe then see if number of messages stuck on the transmission queues are very different. Just try to rule out the possibilities.
Testers are busy at the moment. Too bad I don't have authority and access to perform the test

JS
Back to top
View user's profile Send private message
hughson
PostPosted: Fri Oct 18, 2013 12:42 am    Post subject: Re: That is what we are going to find out Reply with quote

Padawan

Joined: 09 May 2013
Posts: 1916
Location: Bay of Plenty, New Zealand

lozaza wrote:
we might stop the channels between the app server and mainframe then see if number of messages stuck on the transmission queues are very different

Now you have me extremely worried. I had made the assumption that you were talking about client-conn -> server-conn channels. It appears I made the wrong assumption. If there are transmission queues in the picture, then I guess you are talking about sender-receivers. Please be aware that using a connection balancer such as F5 between queue manager to queue manager channels is unsupported, except in some very narrow cases. Can you confirm your scenario please? Where is this F5 in the picture?

Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General Discussion » potential MQ performance issue
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.