|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Guidelines for number of Queues per CF Structure? |
« View previous topic :: View next topic » |
Author |
Message
|
dogbert64 |
Posted: Fri May 08, 2009 10:58 am Post subject: Guidelines for number of Queues per CF Structure? |
|
|
Acolyte
Joined: 11 Jun 2003 Posts: 58
|
Well, I've got my first QSG up and running, with some queues which have been migrated to Shared Queues and I have both Sending and Receiving Shared Channels working as well. So far, everything has been working just as IBM has advertised...I am pleased.
All this has been done in our "lowest" environment, but has given me pretty much all the knowledge I need to move QSG up through the higher environments and onto PROD.
Only the best practice questions remain for me. The current one I am chewing over is: How many CF Structs should be built for Production Queues?
I created CFSTRUCT level 4 by the way.
IIRC there is a 512 queue limit for a single CFStruct and we probably have about 200 queues in PROD, so that's really not a driving factor...at least not now.
What is everyone else doing?
Would I be better off throwing all the queues into one big-honkin' CFStruct or segregating them by short-lived msgs vs long lived msgs? Or maybe by some other criteria?
It seems to be to have one big CFStruct might be the easiest way to go from Admin viewpoint, but what about performance?
Since you have to still specify a STGCLASS on a Shared Queue Definition, and since Shared Queues don't live in Pagesets, I am assuming that the STGCLASS property still is needed by MQ to determine which Buffer Pool to use on the way to the Coupling Facility.
So if that is true, would that play into the decision?
Just trying to get some suggestions and viewpoints here.
Thanks. |
|
Back to top |
|
 |
bob_buxton |
Posted: Fri May 08, 2009 11:38 am Post subject: |
|
|
 Master
Joined: 23 Aug 2001 Posts: 266 Location: England
|
You might want to separate queues with persistent messages into one structure (and back it up frequently).
You could also consider splitting based on message size.
Like all queues it is best to avoid long lived messages where possible.
Shared messages don't go via buffer pools so the storage class is not used (unless using the queue with the IMS bridge) _________________ Bob Buxton
Ex-Websphere MQ Development |
|
Back to top |
|
 |
dogbert64 |
Posted: Thu May 28, 2009 6:04 am Post subject: |
|
|
Acolyte
Joined: 11 Jun 2003 Posts: 58
|
Thanks Bob for the reply. I just read in the Concepts manual where it states that the messages in the Shared Queues do not use Buffer Pools, so I must have missed that the first time I read it. Thanks for straightening me out on that.
Also, all of our messages in the Shared Queues will be persistent, so I won't be able to segregate on that. |
|
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
|
|
|
|