Does using a shared container affect job performance in any way?
In my current example, I'm facing an ugly string of lookup stages (i.e. the Reject link records for the first lookup stage must be the input records for a subsequent lookup stage with a slightly different match criteria, and so on), but I could instead group some of the lookup stages into a shared container and reuse that container many times. It would certainly be easier from a coding and maintenance perspective, but is there a performance impact to having many shared containers in the same job?
Shared Container Performance
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 4
- Joined: Wed Mar 26, 2008 2:34 pm