Hi,

In dynamic process, I read about two models: Client server and parent child.

Client Server : We need to have dedicated threads each for client and server. Now considering all instances same , we will end up doing lot of thread creation apart from our application worker threads. Moreover when 1 instance (app) goes down, we want that instance to come up without doing much manual work. We don't want to club this logic in our application.

Also, When I took the size(number of instance for that comm), I am not getting the count for client instance. To distribute the task, I need to have additional logic to handle this case in my application.

2) Parent child: Suppose we have started 4 instance on 4 different machines. Now we need to add another server. I don't think parent child/ client server is good option in this case.

We don't want to build process management capabilities in our application. We are looking for process management in MPI itself (e.g in Hydra )so that we can leverage on that.

Please correct me if I am missing something in my understanding of Dynamic model. 

Regards

Sanjeev Sinha