05-18-07 12:19 PM
Hi Shiri,
Limiting the number of orhcestration instances within BizTalk is still not a
readymade soltuion. Example: There is no simple way to just go and configure
the number of instance for a particular Orchestration.
If you need to limit the number of orchestration instances, then you need to
do some design pattern like singleton orchestration (only one instance) or
some controller orchestration which executes prior to your original orch kic
k
off etc.
Throttling is completely different, in simple terms it's just controling the
overall performance of the system like setting some threshold limits like
"In-fligh messages per CPU", "Database Latency" ,"Message publishing", etc
It's not advisable to change the default settings, unless otherwise you have
dedicated performance team to tweak to your requirements with rigorous
testing.
HTH
--
Regards,
Saravana Kumar
http://www.biztalk247.com/v1/
http://www.digitaldeposit.net/blog
[Please mark the response as "Answer" if it solves your problem.]
"Shiri" wrote:
> Hi,
>
> I have a client that needs to limit the orchestration instances. The
> throttling configuration, a new feature at BTS06 can be helpful for that
> issue.
> What is the exact configuration? Is it the CPU thread parameter?
> Talking about BTS application group, 2 servers, 2 CPU's each. Do we have t
o
> set that value to 4? (2X2, 4 instaces concurrent).
>
> TIA,
> Shiri
>
>
>
[ Post a follow-up to this message ]
|