| Author |
Message
|
| Yanghui |
 Posted: Wed Jun 11, 2003 2:35 am Post subject: The maximum number of the nodes a message can go through |
 |
|
Disciple
Joined: 08 May 2002
Posts: 151
Location: Dublin, Ireland
|
Hi,
I got this impression that there is a limitation of the number of the nodes a message can go through within a message flow. The impression is about 400 something. Does anybody know exactly how the limitations are, such as 100 compute nodes only, or 800 Filter nodes? Where can I find the information?
Thanks a lot in advance.
-Yanghui |
|
| Back to top |
|
 |
| wmqiguy |
| Posted: Wed Jun 11, 2003 5:49 am Post subject: |
|
|
Centurion
Joined: 09 Oct 2002
Posts: 145
Location: Florida
|
From the technician side, I think this is an interesting question and does anybody have the answer? My gut says that this is more a limitation on resources of the particular platform (memory, etc.) and not on the product itself.
From the business side, I'm wondering when anybody would need 100 Compute nodes? If so, that sounds like one interface that needs an army of coders. Also, hundreds of filters sounds like a great candidate for a destination list.
Has anybody ever bumped into needing 100's of nodes? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 11, 2003 6:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The sense I get is that how many nodes you can string along in a row depends a lot on what those nodes are doing.
I also get the sense that there isn't a hard fixed limit, just a performance drop-off point.
So, I'd say it's extremely dependant on what your flow is doing and where it's running.
The other thing to be aware of is that as you add nodes to a message flow, you increase the size of the XML deployment description. Since that XML is given to the broker over MQSeries, it can only be as big as a single MQSeries message (up to 100 MBs). So that's another more fixed limitation on the number of nodes you can put in. Again, though, it depends on what the node is doing (as that affects the size of the XML stanza describing the node). |
|
| Back to top |
|
|
| Yanghui |
| Posted: Wed Jun 11, 2003 7:47 am Post subject: |
|
|
Disciple
Joined: 08 May 2002
Posts: 151
Location: Dublin, Ireland
|
Thanks for replys.
It's quite easy for a message flow to have more than 100 nodes. In my previous WMQI project, I did one msgflow with more than 200 nodes.
I think why this is brought in picture is that each time a msg goes through a node, broker has to remember all the data in trees both in and out all the way through just in case back-out happens. I don't think it's unlimited.
I did read something about this somewhere but don't remember anymore.
Yes, I have to use a lot of filter nodes since RouteToLabel and Lablel nodes can't be used in subflow if mainflow refers it twice.
I am setting up a matrix to get a generic-ish solution for SWIFT but so afraid of hitting this limitation. I will see how far I can stretch it.
-Yanghui |
|
| Back to top |
|
|
| fschofer |
| Posted: Thu Jun 12, 2003 6:55 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
|
| Back to top |
|
|
| Yanghui |
| Posted: Fri Jun 13, 2003 7:54 am Post subject: |
|
|
Disciple
Joined: 08 May 2002
Posts: 151
Location: Dublin, Ireland
|
It's always good to know limition before hand.
I am wondering if there is a way to trace how many nodes one message travels through within a msgflow. I know I can get the information by switching trace on but it's not straight forward. Any idea about how to achieve this? or to monitor the stack space used by broker?
Regards
-Yanghui |
|
| Back to top |
|
|
|
|
