| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Collector node and multiple instances |
« View previous topic :: View next topic » |
| Author |
Message
|
| kenward |
 Posted: Thu Jul 28, 2011 10:07 am Post subject: Collector node and multiple instances |
 |
|
Apprentice
Joined: 01 Jun 2010
Posts: 41
Location: Detroit, MI
|
Hi,
We're using WMB V7 (latest FP) and I have a Flow with 4 additional instances set up.
The flow is basically:
MQInput -> Collector -> ComputeNode -> SoapRequest
The collector is configured to complete after 250 messages.
Under load of 10000 messages to the MQInput node (putting them there as fast as they'll take them), The Collector seems to just output one collection at a time as it completes 250.
Our expectation is that 5 collections would be populated at once and that we should be seeing 5 Soap Requests fire about the same time.
We definitely see 4 additional instances on the flow that's deployed.
Any idea what may be causing this behavior? |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Thu Jul 28, 2011 10:44 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Under the hood, the Collector node used two queues.
SYSTEM.BROKER.EDA.*
One for the messages that go into the collection. One for the collection itself, when it is complete.
The collector node is actually to distinct parts.
The bit that collects things.
The bit that builds the completed collection and sends it out.
You need to make sure that the SYSTEM.BROKER.EDA.* queues aren't becoming full.
Home many cores/threads does your system have? If you have configured more instances than there are threads available then you won't get any performance increase.
You need to take your time and do a lot of incremental testing to build up a realistic picture of your workload. There will be a sweet spot that gives you the best throughput.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jul 28, 2011 11:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I am not sure there is currently a way to add additional instances to the output side of the collector node.
If there is a way, it will be as a property on the collector node itself. |
|
| Back to top |
|
|
| kenward |
| Posted: Thu Jul 28, 2011 11:51 am Post subject: |
|
|
Apprentice
Joined: 01 Jun 2010
Posts: 41
Location: Detroit, MI
|
So would multiple collector nodes all feeding off the same MQInput work?
I know that would limit us to redeployments every time we wanted to change the number of instances, but right now, I just need to get this to work. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jul 28, 2011 12:24 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| If you don't care which 250 messages are in a given colleciton, then, yes, multiple collector nodes will give you multiple output threads, potentially simultaneously. |
|
| 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
|
|
|
|
