I've stumbled into an unexpected situation.I'm observing significant performance differences depending on how a child Package is launched.Scenario 1 : Single Master Package calling Specific PackagesScenario 2 : ETL Framework approach - Specific package is a few layers in (nested child packages).I would expect some initial overhead with scenario 2, but once the base package is running, I would expected performance to be similar.WHat I've found is performance of the base packages is significantly better with scenario 1.For Example : Same server, same data, etc.Scenario 1 : 1 minutes.Scenario 2 : 10 minutes.There does not appear to be any "problem" step .... all the steps are slowed in Scenario 2.I even looked at a step that didn't need any datebase - all it does is use variables to build a file path.Scenario 1 : 1 secScenario 2 : 7 sec.Any thoughts ?Is it possible that have multiple packages open in scenario 2 causes the system to reach a point where even variables are being written to disk?Is there some threshold of "active packages" that I may have hit ?
↧