Keeping Orchestration alive

You could use a loop shape with a Sequential Convoy.  But you could run into some other issues.  I’d only do this if your business process required it… not for any type of performance reason.

For a performance point of view, I think it’s just the first time you run an Orchestration after a Host restart that has the huge performance hit. 

Hope this helps.

David-

What you are experiencing only occurs the first execution after a host restart, which on a production server should be infrequently. Like any other .NET application BizTalk assemblies are only compiled to MSIL. On first execution JIT compilation takes place so it takes a bit longer than usual to execute. I don’t know of any work around and it is in my understanding happening “as designed”.

For this reason I suggest that before doing any perf testing, (or before demoing BizTalk to others) that you run sample messsages all the way through the process, (JIT happens more granularly than the assembly level). This will get the JIT "out of the way" and be ready to rock!