We have a BizTalk 2004 Orchestration which implements the broker pattern to
call two web services on other systems and return a consolidated reply. The
Orchestration itself is exposed as a web service using the Wizard buily into
BizTalk.

All web services are configured such that they never unload and I have set
the MaxReceiveInterval for XLANGs etc to 100ms. In addition I have set the
SecondsIdleBeforeShutdown and SecondsEmptyBeforeShutdown options in the
config file to -1 (never shutdown).

Initially the transaction rate through this Orchestration will be very low
and we are finding that the first reponse from the Orchestation can be very
slow (4-5 seconds). Subsequent responses are much faster (around 0.9
seconds). What we have found is that if BizTalk does not process anything fo
r
a few minutres we get the slow initial response again and then BizTalk seems
to speed up again.

Is there anything I can do to remove the slow response to the initial reques
t?

[ Post a follow-up to this message ]

Hello NigelT,

This may not help you but I thought I would mention it anyway.

There is a registry key which controls batching called HttpBatchSize.

If you set that to 1, you will get a faster response, this solved a performa
nce
problems once for me.

BA
http://biztalkia.blogspot.com/


> We have a BizTalk 2004 Orchestration which implements the broker
> pattern to call two web services on other systems and return a
> consolidated reply. The Orchestration itself is exposed as a web
> service using the Wizard buily into BizTalk.
>
> All web services are configured such that they never unload and I have
> set the MaxReceiveInterval for XLANGs etc to 100ms. In addition I have
> set the SecondsIdleBeforeShutdown and SecondsEmptyBeforeShutdown
> options in the config file to -1 (never shutdown).
>
> Initially the transaction rate through this Orchestration will be very
> low and we are finding that the first reponse from the Orchestation
> can be very slow (4-5 seconds). Subsequent responses are much faster
> (around 0.9 seconds). What we have found is that if BizTalk does not
> process anything for a few minutres we get the slow initial response
> again and then BizTalk seems to speed up again.
>
> Is there anything I can do to remove the slow response to the initial
> request?
>

[ Post a follow-up to this message ]

Nigel,

If you are seeing slower performance on the first request and after periods
of inactivity, this is probably due to .NET cleanup behavior.  You may be
able to edit the BTS config file to never unload the app domain, but I do
not know yet if this is supported.  I will look into this and see as I have
other customers asking the same question.

Regards,
Doug Girard [MSFT]

Note: This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
>Thread-Topic: Slow response to first Request
>thread-index: AcYgA+sjw6PTTgSIT2y7PaEjoZhDqQ==
>X-WBNR-Posting-Host: 213.137.3.102
>From: examnotes <NigelT@discussions.microsoft.com>
>Subject: Slow response to first Request
>Date: Mon, 23 Jan 2006 02:01:02 -0800
>Lines: 20
>Message-ID: <85A09149-F59B-419D-A045-C03EED8F35CC@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>	charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.biztalk.general
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.biztalk.general:34221
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>We have a BizTalk 2004 Orchestration which implements the broker pattern
to
>call two web services on other systems and return a consolidated reply.
The
>Orchestration itself is exposed as a web service using the Wizard buily
into
>BizTalk.
>
>All web services are configured such that they never unload and I have set
>the MaxReceiveInterval for XLANGs etc to 100ms. In addition I have set the
>SecondsIdleBeforeShutdown and SecondsEmptyBeforeShutdown options in the
>config file to -1 (never shutdown).
>
>Initially the transaction rate through this Orchestration will be very low
>and we are finding that the first reponse from the Orchestation can be
very
>slow (4-5 seconds). Subsequent responses are much faster (around 0.9
>seconds). What we have found is that if BizTalk does not process anything
for
>a few minutres we get the slow initial response again and then BizTalk
seems
>to speed up again.
>
>Is there anything I can do to remove the slow response to the initial
request?
>
>
>

[ Post a follow-up to this message ]