ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Restriction on number of compute nodes in msgflow

Post new topic  Reply to topic
 Restriction on number of compute nodes in msgflow « View previous topic :: View next topic » 
Author Message
kishoreraju
PostPosted: Fri Sep 05, 2008 11:23 am    Post subject: Restriction on number of compute nodes in msgflow Reply with quote

Disciple

Joined: 30 Sep 2004
Posts: 156

hi all,

Is There any restriction on number of compute nodes that we can use in flow.
Back to top
View user's profile Send private message
chrisc
PostPosted: Sun Sep 07, 2008 3:40 pm    Post subject: Reply with quote

Voyager

Joined: 19 Mar 2006
Posts: 77

I haven't heard of - or come across - any limitation on the number of compute nodes, but what we have observed is that increasing the number of compute nodes exponentially increases the amount of memory required.

I'm not sure of the exact numbers, but it may be something like 5-10% extra memory per compute node.

My understanding is that this is because any node that has InputXXX and OutputXXX message trees keeps a copy of both the input and output for the purposes of rolling them back if there is an exception. This can add up rapidly, particularly if you are dealing with large messages. (Keep in mind that a small physical message on a queue can turn into a substantial amount of memory in the broker by the time all the parsing etc has been done.)

If you need to split your logic across many nodes, one alternative is to use non-transforming nodes where you are doing logic but not message transformation. For example, a filter node or a database node can manipulate the Environment tree but not the message, but this may be sufficient for what you're trying to do.

Hope that helps.

(There may ALSO be a limitation on compute nodes, but I've neveer reached it and would suggest you're designing your flows wrong if you do hit it!)
Back to top
View user's profile Send private message
kishoreraju
PostPosted: Mon Sep 08, 2008 5:39 am    Post subject: Reply with quote

Disciple

Joined: 30 Sep 2004
Posts: 156

Thanks for ur quick response.

Even i never heard anything like this type of restriction.To be sure i posted this question.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Restriction on number of compute nodes in msgflow
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.