BizTalk 2006 orchestration throughput decreased over time   

Windows 2003 SP2, BizTalk 2006 Standard with database on SQL 2005 Standard 
(clustered)

This BT server was configured as one singleton BizTalk orchestration to 
control the number of active instances and to route the messages to other 
orchestrations.

Each receive location will spawn singleton orchestration instance.
Each receive location will have short poll interval (1 - 10 seconds) and 
poll quite large rows of data (10 - 50 rows) because of the high frequency of 
the application.  
 
Over time after startup, processing performance became slower for the 
orchestrations

1. Sending the message From MessageBroker to the orchestrations (A, B, C, D) 
becomes slower
2. Processing time for the orchestrations (A, B, C, D) are also affected and 
subsequently drops.

For instance, in the first hour the orchestration A could process 40 message 
per minute in average, but then dropped to  20 message/minute in the second 
hour; and after several hours trickled to 1 message/minute
 
If the workaround of using direct binding from the receive location to the 
respective orchestrations (instead of via MessageBroker) then the performance 
was consistent over several hours i.e. 40 message / minute

BizTalk FAQ http://technet.microsoft.com/en-us/library/bb418739.aspx 
mentioned the hotfix KB912276 for BizTalk 2004.

Is there one for BizTalk 2006?

Currently, the module version on this server is  "3.5.1602.0"

Thanks for any remedial help


Hong

date: Tue, 6 May 2008 02:01:00 -0700   author:   Hong

RE: BizTalk 2006 orchestration throughput decreased over time   

Hello Hong,

You should take a look at the cost of the persistence of your Singleton 
Orchestration.
You can do this with the SQL Profiler - you wan't to capture execution of 
bts_InsertDynamicStateInfo_YourApplication.
Then in the trace you can export the data and look at its size.

Bests Regards,
Roch

"Hong" wrote:

> Windows 2003 SP2, BizTalk 2006 Standard with database on SQL 2005 Standard 
> (clustered)
> 
> This BT server was configured as one singleton BizTalk orchestration to 
> control the number of active instances and to route the messages to other 
> orchestrations.
> 
> Each receive location will spawn singleton orchestration instance.
> Each receive location will have short poll interval (1 - 10 seconds) and 
> poll quite large rows of data (10 - 50 rows) because of the high frequency of 
> the application.  
>  
> Over time after startup, processing performance became slower for the 
> orchestrations
> 
> 1. Sending the message From MessageBroker to the orchestrations (A, B, C, D) 
> becomes slower
> 2. Processing time for the orchestrations (A, B, C, D) are also affected and 
> subsequently drops.
> 
> For instance, in the first hour the orchestration A could process 40 message 
> per minute in average, but then dropped to  20 message/minute in the second 
> hour; and after several hours trickled to 1 message/minute
>  
> If the workaround of using direct binding from the receive location to the 
> respective orchestrations (instead of via MessageBroker) then the performance 
> was consistent over several hours i.e. 40 message / minute
> 
> BizTalk FAQ http://technet.microsoft.com/en-us/library/bb418739.aspx 
> mentioned the hotfix KB912276 for BizTalk 2004.
> 
> Is there one for BizTalk 2006?
> 
> Currently, the module version on this server is  "3.5.1602.0"
> 
> Thanks for any remedial help
> 
> 
> Hong
>

date: Sun, 18 May 2008 03:24:00 -0700   author:   Roch Baduel