Posted: Thu Sep 12, 2002 4:44 am Post subject: Using single DataStructure across the process
Disciple
Joined: 03 Apr 2002 Posts: 166 Location: VA, USA
Consider the following case..
There is a process which contain 5 activities. Each Activity has 2 element in the datastructure. Suppose for each activity I define a distinct datastructure. Then that process will have 5 distinct datastructures.
Consider the second scenario....For the same process I create a single datastructure which contain 10 elements ( I merged 5 datastructers into a single one) and assign to each activity. Now I may be using only two elements in datastrcture at each activity.
My question is how workflow server behave behind the scene for both the cases when I create & start process instance. From the workFlow performance point of view which is better....
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
It is my opinion that the biggest effect is the database footprint. When dealing with a structure containing only 10 members (assuming reasonable sizes for all) I think it is moot. However, when you have a 30 activity Template, with 100 or so different fields, only 5 or 6 of which are used at each activity, I would definitely go with separate data structures. _________________ John McDonald
RETIRED
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