| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Queue definitions and other performance settings... |
« View previous topic :: View next topic » |
| Author |
Message
|
| kramsnilloc |
 Posted: Thu Nov 08, 2007 5:39 am Post subject: Queue definitions and other performance settings... |
 |
|
Newbie
Joined: 23 Aug 2007
Posts: 8
Location: Jacksonville, FL.
|
Now that I have my "Pseudo Synchronous MQ Call on z/OS using COBOL"
http://www.mqseries.net/phpBB2/viewtopic.php?t=39113
[ulr]http://www.mqseries.net/phpBB2/viewtopic.php?t=39493[/url]
program working, I'm now in the tuning stage. When running tests, I'm seeing a round trip message taking upwards of 6 seconds (keep in mind that this is a 'test' environment).
The queue definitions are below. One setting I'm wondering about is the Default share option = S. Since my service is the only one using this set of queues, should they be set to Exclusive?
To recap; my COBOL process PUTs a message on the request queue. A Sonic ESB is listening and takes the request routes it to the service which processes it and returns the result in the Response queue.
incite on any of these setting would be greatly appreciated.
| Code: |
xxx.xx.DV2U.LOCATION.REQUEST
[size=9]Queue name . . . . . . . . . xxx.xx.DV2U.LOCATION.REQUEST
Disposition . . . . . . . . : QMGR CXQ2
Description . . . . . . . . : Location Service Request Queue
for DV2U
Put enabled . . . . . . . . : Y Y=Yes, N=No
Get enabled . . . . . . . . : Y Y=Yes, N=No
Usage . . . . . . . . . . . : N N=Normal, X=XmitQ
Storage class . . . . . . . : ATTACH
CF structure name . . . . . :
Dynamic queue type . . . . : N N=Non-dynamic (Predefined), T=Temporary,
P=Permanent, S=Shared
Cluster name . . . . . . . :
Cluster namelist name . . . :
Default bind . . . . . . . : O O=Open, N=Notfixed
Cluster workload rank . . . : 0 0 - 9
Cluster workload priority . : 0 0 - 9
Cluster workload queue use : Q A=Any, L=Local, Q=Qmgr
Default persistence . . . . : N Y=Yes, N=No
Default priority . . . . . : 0 0 - 9
Message delivery sequence . : P P=Priority, F=FIFO
Permit shared access . . . : Y Y=Yes, N=No
Default share option . . . : S E=Exclusive, S=Shared
Index type . . . . . . . . : N N=None, M=MsgId, C=CorrelId, G=GroupId,
T=MsgToken
Maximum queue depth . . . . : 6000 0 - 999999999
Maximum message length . . : 8000000 0 - 104857600
Trigger Definition
Trigger type . . . . . . : N F=First, E=Every, D=Depth, N=None
Trigger set . . . . . . : N Y=Yes, N=No
Trigger message priority : 0 0 - 9
Trigger depth . . . . . : 1 1 - 999999999
Initiation queue . . . . :
Process name . . . . . . :
Trigger data . . . . . . :
Event Control
Queue full . . . . . . . : E E=Enabled, D=Disabled
Upper queue depth . . . : E E=Enabled, D=Disabled
Threshold . . . . . . . : 80 0 - 100 %
Lower queue depth . . . : D E=Enabled, D=Disabled
Threshold . . . . . . . : 40 0 - 100 %
Service interval . . . . : N H=High, O=OK, N=None
Interval . . . . . . . . : 999999999 0 - 999999999 milliseconds
Backout Reporting
Backout threshold . . . : 0 0 - 999999999
Harden backout counter . : N Y=Yes, N=No
Backout requeue name . . :
Retention interval . . . . : 999999999 0 - 999999999 hours
Monitoring . . . . . . . . : Q Q=Qmgr, L=Low, M=Medium, H=High, O=Off
Accounting . . . . . . . . : Q E=Enabled, D=Disabled, Q=Qmgr
xxx.xx.DV2U.LOCATION.RESPONSE
Queue name . . . . . . . . . xxx.xx.DV2U.LOCATION.RESPONSE
Disposition . . . . . . . . : QMGR CXQ2
Description . . . . . . . . : Location Service Response Queue
for DV2U
Put enabled . . . . . . . . : Y Y=Yes, N=No
Get enabled . . . . . . . . : Y Y=Yes, N=No
Usage . . . . . . . . . . . : N N=Normal, X=XmitQ
Storage class . . . . . . . : ATTACH
CF structure name . . . . . :
Dynamic queue type . . . . : N N=Non-dynamic (Predefined), T=Temporary,
P=Permanent, S=Shared
Cluster name . . . . . . . :
Cluster namelist name . . . :
Default bind . . . . . . . : O O=Open, N=Notfixed
Cluster workload rank . . . : 0 0 - 9
Cluster workload priority . : 0 0 - 9
Cluster workload queue use : Q A=Any, L=Local, Q=Qmgr
Default persistence . . . . : N Y=Yes, N=No
Default priority . . . . . : 0 0 - 9
Message delivery sequence . : P P=Priority, F=FIFO
Permit shared access . . . : Y Y=Yes, N=No
Default share option . . . : S E=Exclusive, S=Shared
Index type . . . . . . . . : C N=None, M=MsgId, C=CorrelId, G=GroupId,
T=MsgToken
Maximum queue depth . . . . : 5000 0 - 999999999
Maximum message length . . : 8000000 0 - 104857600
Trigger Definition
Trigger type . . . . . . : N F=First, E=Every, D=Depth, N=None
Trigger set . . . . . . : N Y=Yes, N=No
Trigger message priority : 0 0 - 9
Trigger depth . . . . . : 1 1 - 999999999
Initiation queue . . . . :
Process name . . . . . . :
Trigger data . . . . . . :
Event Control
Queue full . . . . . . . : E E=Enabled, D=Disabled
Upper queue depth . . . : E E=Enabled, D=Disabled
Threshold . . . . . . . : 80 0 - 100 %
Lower queue depth . . . : D E=Enabled, D=Disabled
Threshold . . . . . . . : 40 0 - 100 %
Service interval . . . . : N H=High, O=OK, N=None
Interval . . . . . . . . : 999999999 0 - 999999999 milliseconds
Backout Reporting
Backout threshold . . . : 0 0 - 999999999
Harden backout counter . : N Y=Yes, N=No
Backout requeue name . . :
Retention interval . . . . : 999999999 0 - 999999999 hours
Monitoring . . . . . . . . : Q Q=Qmgr, L=Low, M=Medium, H=High, O=Off
Accounting . . . . . . . . : Q E=Enabled, D=Disabled, Q=Qmgr [/size] |
Thanks for any response...
Mark
Last edited by kramsnilloc on Thu Nov 08, 2007 5:46 am; edited 1 time in total |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Nov 08, 2007 5:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I doubt changing the queue setting as you describe is going to make a significant difference.
You're better off performing a general tuning exercise using the information contained in the various redbooks and white papers on the subject, as held by the IBM website.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kramsnilloc |
| Posted: Thu Nov 08, 2007 5:49 am Post subject: |
|
|
Newbie
Joined: 23 Aug 2007
Posts: 8
Location: Jacksonville, FL.
|
Can you give me any key words to google, or direct me to a specific topic? I tried several to no avail...
Thanks again,
Mark |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Nov 08, 2007 6:27 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
The Shared queue option doesn't affect performance.
You want to check you are using non-persistent messages (assuming that is OK). This is not just the queue attribute (which is only the default if not specified on the MQPUT).
You want to check if the Sonic adapter has a MQGET WAIT outstanding so that it will immediately get the message. If it "polls" (timer based) then you will get average latency of half the poll interval added to the processing.
Test the application in parts using something like RFHUTILC to simulate the other part and identify where the latency is being added.
My guess would be in the Sonic adapter, so trace the MQI calls (support pac). |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Nov 08, 2007 7:02 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
| kramsnilloc |
| Posted: Thu Nov 08, 2007 8:12 am Post subject: |
|
|
Newbie
Joined: 23 Aug 2007
Posts: 8
Location: Jacksonville, FL.
|
|
| 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
|
|
|
|
