Posted: Wed Aug 15, 2007 10:37 am Post subject: Project reference
Voyager
Joined: 05 Aug 2002 Posts: 79 Location: US
Hi,
I'm using MB 5.0. In my message flow project I've include a project which contains all the common routines as project reference. After I did this the bar file size was considerably big and hence I opened the .cmf file to check the content of it. To my surprise, the esql procedures in the common project was copied multiple times as the number of compute node in my message flow. Is there a way to avoid this? This directly results in the execution group allocating more memory while I deploy my bar file. My bar file size is around 600KB and the the EG allots around 11MB as soon as I deploy the flow without even processing any message.
All contents of a broker schema are included in every compute node that uses ANY portion of that broker schema.
This means ... "keep your broker schemas small". It also means "put as little as possible into the default schema". _________________ I am *not* the model of the modern major general.
Thanks for the reply jeff. But only in one of my compute node I'm using the procedures from the referenced project. All other compute nodes doesnt have any reference to the broker schema. Even then, the broker schema is getting included!!!
Or maybe I'm confusing it with "new features of MB v6".
Make sure you're at the latest version of the v5 Toolkit.
And I hope you're planning the migration to v6 soon. You've got only another year before v5 goes out of support. _________________ I am *not* the model of the modern major general.
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