Rambling on about 64 bit issue I had...
I have done various tests. I developed a simple package (which moves files from source directory to working directory) to test timing against RTM, and the same process against SP1 and then Hotfix. The differences were negligible, between different builds. So I opened my original package and disabled all the tasks except the one I have built in the simple package and executed it and the difference was huge.
Simple package took around ~ 18 seconds to moves files etc where my master package took around ~ 270 seconds. Infact it was 15 times slower.
Then I went back drawing board as they say and looked at what was going on, specially what are the differences between simple package against the master package originally developed. My first instinct was event handlers and I disabled them and the performance was negligible . Second thought was transaction and that didn't make any difference. Next thing came to my mind was checkpoint and that wasn't an issue either. At this point I was going mad.....!!!!!!
While checking both packages visually I noticed something quite different. The simple package has only 2 connections where the master package had quite a few (close to 100 connections). Then I reproduced it and it seems to be the problem.
So, my initial conclusion is that Execute Package Task seems to be resolving package configurations each time it loads / execute a package on a 64 Bit environment. The behaviour seems to be totally different on a 32 bit environment.
We have logged a call with MS about this.
Keep you posted.
Thanks
Sutha
Simple package took around ~ 18 seconds to moves files etc where my master package took around ~ 270 seconds. Infact it was 15 times slower.
Then I went back drawing board as they say and looked at what was going on, specially what are the differences between simple package against the master package originally developed. My first instinct was event handlers and I disabled them and the performance was negligible . Second thought was transaction and that didn't make any difference. Next thing came to my mind was checkpoint and that wasn't an issue either. At this point I was going mad.....!!!!!!
While checking both packages visually I noticed something quite different. The simple package has only 2 connections where the master package had quite a few (close to 100 connections). Then I reproduced it and it seems to be the problem.
So, my initial conclusion is that Execute Package Task seems to be resolving package configurations each time it loads / execute a package on a 64 Bit environment. The behaviour seems to be totally different on a 32 bit environment.
We have logged a call with MS about this.
Keep you posted.
Thanks
Sutha
1 Comments:
At 2:09 AM, Sutha Thiru said…
Microsoft at Reading has reproduced the same scenario. They executed a small configuration file package within 20 seconds where the large configuration file package took over 5 mins.
So we can re-pro. This will go to dev team in Redmond soon. Keep you posted what they say.
Thanks
Sutha
Post a Comment
<< Home