| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Performance Management in API Calls |
« View previous topic :: View next topic » |
| Author |
Message
|
| amateur |
 Posted: Thu Mar 10, 2005 5:09 am Post subject: Performance Management in API Calls |
 |
|
Novice
Joined: 29 Nov 2004
Posts: 11
|
Hi,
I am writing a Java Code to transfer messages from 60 source Queues to the corresponding 60 Destination Queues (60 queue pairs) in a queue manager.
I have two ways to achieve this.
Option 1:
1. Open all (60 source Queues + 60 Destination Queues) at once.
2. Get and PUT the messages in a queue pair (from one source Queue and to the corresponding Destination Queue).
3. At the end close all (60 source Queues + 60 Destination Queues) together.
Option 2:
1. Open a queue pair (Source and Destination Queue).
2. Transfer the messages and Close both the queues.
3. For the second set again open the source Queue and its corresponding Destination Queue, transfer the messages and close it.
Do Open and Close for all the 60 pairs seperately.
Of the two options, which is better in terms of the performance?
i.e Keeping open all the 120 Queues, transfer all the messages and Close all at once. (or)
Open a pair of queues, transfer messages and close it; Open another pair of queues and so on....
Please let me know your Ideas on this. Or Is there a better way to handle this job?
Thanks in Advance.
_________________
Regards,
Amat |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Thu Mar 10, 2005 5:42 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Since i'm not very sure of what ur trying to do, i would say the second option is better of the two u mentioned.....
First of all the connection handles will be less and also other users will have a faster access to ur, all but one queues.......since u wont sit and occupy them all at once.
BUT
Isn't it a better idea to just make sender channels and let the messages go as and when they come.....
u could also set a trigger if u want this operation to occur only after certain queue depth..... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 10, 2005 5:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You're better off doing one queue at a time. Especially if you are using syncpoint - keeping sixty queues with who knows how many messages on them open in sixty units of work will drive your admins crazy (and putting all of them in the same unit of work would be even worse).
But it sounds like your MQ network isn't set up to do the work for you, which it should be. A well built MQ network wouldn't require you to write code to move messages to the place they belong.
If you're doing this to try and time delay your processing, it likely would be better to store the messages in a database, and then rebuild them as needed. This will give you a lot more flexibility about what gets moved where when.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
