| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to design the read/write from queue,one or more threads? |
« View previous topic :: View next topic » |
| Author |
Message
|
| olivieer |
 Posted: Mon Nov 22, 2004 2:58 am Post subject: How to design the read/write from queue,one or more threads? |
 |
|
Newbie
Joined: 17 Nov 2004
Posts: 5
|
Hi,
I have a MQ Server having one queue manager.
The queue manager has 8 queues where i can write, and 14 where i can read.
What should be the best to do :
- 1 thread to read (with a small waiting time) / 1 thread to write
- 14 threads to read (one per queue) / 8 threads to write
- 1 process to read / 1 process to write
- 14 processes to read / 1 process to write
Thanks
Olivier |
|
| Back to top |
|
 |
| KeeferG |
| Posted: Mon Nov 22, 2004 4:55 am Post subject: |
|
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
If performance is an issue then it is much better to have threads waiting for a mesasge to arrive on the queue. That way the queue will be avoided entirely. As for puts it doesn't really matter as the mesasge will always get paassed on be it to the queue or a waiting get thread.
Of course this is all dependent on the type of data being sent and whether each message is atomic.
_________________
Keith Guttridge
-----------------
Using MQ since 1995
Last edited by KeeferG on Mon Nov 22, 2004 5:47 am; edited 1 time in total |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Nov 22, 2004 5:36 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The decision of how many processes and threads you have involved has really nothing to do with the number of queues, except indirectly.
You should have as many different processes as you have logical sets of functionality (process orders, service loans, format reports, whatever), based on the business you are performing.
Then each process should have sufficient threads within it to achieve the performance it needs to deliver.
Each application/process should read and write to as many queues as are appropriate, again based on the functions you are trying to perform.
In other words, design your systems to meet the business needs, and then use that design to figure out how many queues you need to read and write from in each application.
At least, in my opinion.
_________________
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
|
|
|
|
