| Author |
Message
|
| gssethi |
 Posted: Tue Sep 06, 2005 4:25 am Post subject: Single datastructure for multiple process ? |
 |
|
Newbie
Joined: 06 Sep 2005
Posts: 2
|
| Is this good idea to use a single datastructure (container) for more than one process ? Will this increases the system performance if there are large number of process instances for the template. |
|
| Back to top |
|
 |
| jmac |
| Posted: Tue Sep 06, 2005 5:33 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
In my opinion, NO. Each activity should have only the memebers that are needed in its input container, and only the memebers that are needed in its output container. This will decrease the size of the database footprint. and it is .02 BWU for each user-defined member in the container as I recall.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| gssethi |
| Posted: Wed Sep 07, 2005 8:59 pm Post subject: same datastructure used by more than one process |
|
|
Newbie
Joined: 06 Sep 2005
Posts: 2
|
Hi jmac,
Thanks for the reply. But my doubt is that is it a good idea to use the same datastructure for more than one process if all the fields in the datastructure required by the processes is same. |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Wed Sep 07, 2005 11:12 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
| It wouldn't make sense to create a data structure for a container with the same fields. You should use the same. |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Sep 08, 2005 5:49 am Post subject: Re: same datastructure used by more than one process |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| gssethi wrote: |
Hi jmac,
Thanks for the reply. But my doubt is that is it a good idea to use the same datastructure for more than one process if all the fields in the datastructure required by the processes is same. |
IF all of the members are used for both input and output in ALL activities then I agree. Generally using the same structure for an entire process model is fine for a quick demo or some such. AND using the same structure is ALWAYS easier for the modeler. There is no doubt that having memebers in a data structure that are not used costs in performance, and size of the database. Being more concerned with performance in a production environment I choose to only have what is necessary in the input and output containers for each activity. This is purely my opinion.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
