Sree,
I recommend picking up "Professional BizTalk Server 2006" by Jefford,
Smith and Fairweather. You can get it from Amazon here:
http://tinyurl.com/yt4j4y
They have a great chapter on performance tuning. The short version is
that while you have some control, the guaranteed way to make BizTalk
start more Orchestrations is more CPUs (and/or Boxes in the group) and
more Memory.
Also, you said you're doing a DB query in the orchestration. I would
strongly recommend running a SQL Profiler trace on your database and
make sure you're not slowing down due to locking or the like. I've seen
situations where BizTalk had so many working against the database that
they were in table/page contention with each other.
Tim Rayburn
BizTalk Server MVP
http://TimRayburn.net
Sree wrote:
> It processes only 20 of those orchestrations at any time.... which is
> not much of a load.
>
> This process does a query against a database as the first step.. The
> response is fast on some messages, slow on some. I want to make it so
> that the orchestrations as they get initialized get started with the
> process and query the DB. Any thing that waits on DB may wait but
> messages that can get the reply sooner should not have to wait for its
> turn till BTS picks it up.... Is there a property I can set to start
> more orchestrations so that the ones that get delayed will wait and
> ones that are faster can go ahead...
>
> Thanks
> Sree
>
>
>
> On Jul 6, 10:06 am, Jan Eliasen <elia...@[EMAIL PROTECTED]
> wrote:
>> On Thu, 05 Jul 2007 15:42:34 -0000, Sree <sreej...@[EMAIL PROTECTED]
> wrote:
>>> An orchestration (Instance Orchestration) instantiates the monent it
>>> is called but starts executing after about 8-9 mins from then. I
>>> checked these timings in HAT. Am I missing a setting to get it started
>>> the moment it is instantiated? This orchestration is heavily used in a
>>> running application. Because of this delay in executing I have this
>>> orchestration instances piling up real soon and the processing comes
>>> to s stand still.
>>> Any suggestions on what I am missing or where can I start looking.
>> BizTalk gets to determine what running orchestrations to run at any
>> given moment. Perhaps you ahve too much work for that server, and the
>> orchestration instance must wait for available ressources?
>>
>> Does this occur even if the server and the SQL Server are not very
>> busy?
>>
>> --
>> eliasen, representing himself and not the company he works for.
>>
>> Private blog:http://blog.eliasen.dk
>>
>> Private email: j...@[EMAIL PROTECTED]
|
