| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Performance vs ETX |
« View previous topic :: View next topic » |
| Author |
Message
|
| Hemavathy |
 Posted: Wed Dec 13, 2006 1:22 am Post subject: MQ Performance vs ETX |
 |
|
Newbie
Joined: 06 Dec 2006
Posts: 2
Location: India
|
Applications (Publish and subscribe model) used ETX as middleware.
It's been replaced recently with WebSphere Message Queue (Client Server Model).
The platform is Solaris.
Queue Manager - QM1
Queue Manager - QM2
Messages get transferred between them using SDRC (Sender - Receiver) Channel Pairing.
Design:
Step1: Application A is the client program which puts messages to QM1.
Step2: Messages gets transferred from QM1 to QM2.
Step3: Application B is also a client program which gets the messages from QM2 by polling the queue.
There are many instances of Application A and B running at the same time.
The problem is that the CPU utilization is very high when compared to the previously used ETX middleware.
Please let me know if some other details are needed to solve this issue.
What needs to be looked on to increase the performance of MQ? |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Dec 13, 2006 2:43 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
Find out how many channels are running, please let us know the
output of " ps -ef | grep -i mqm ".
Lets see what and all processes are running
Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Hemavathy |
| Posted: Thu Dec 14, 2006 1:43 am Post subject: |
|
|
Newbie
Joined: 06 Dec 2006
Posts: 2
Location: India
|
The performance issues are in the client program(Application B) which gets messages from QM2.
There is only 1 client server MQI channel.
The processes present in the server machine (QM2 ) are:
3 amqzlaa0 : Queue Manager agent
1 runmqchi : Channel Initiator
1 runmqlsr : Channel listener
1 amqrmppa : Message Channel Agent
1 amqzllp0 : Checkpoint processor
1 amqhasmx : Logger
1 amqzxma0 : Execution controller
1 amqrrmfa : Repository process
1 amqzdmaa : Deffered Message handler
1 amqzfuma : OAM processing
In the server machine, there are also 3 queue managers communicating with other programs.
The problem is that even when there are messages of very small size flowing,
the CPU does not release the client program (Application B ) for a long time. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Thu Dec 14, 2006 2:05 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
I think the Application B is processing the messages very slowly.
as from your message there are only 3 QMgs running in that box,
I dont think that there is any problem with MQ Series running on Solaris
investigate much on the Client application which is picking the message
Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| 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
|
|
|
|
