I created the HTTPReceive subfolder under the
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\BTSSvc.3.0\
in the registry and then added a Dword entry for HttpBatchSize.

I'm not seeing any change in performance, nor any complaints if I set the
value to greater than 256.  How can I be sure that the host has isusing this
tuning value ?

[ Post a follow-up to this message ]

Are you sure this is the correct location please?
Isn't this key related to the actual host?  (In that case you might need to
add the GUID somewhere in the regkey path...)  Please double check the
location since I'm not sure...

Best regards,
Christof

--
Christof [Microsoft BizTalk Server MVP]

"Tim B." <TimBur@seattletimes.com> wrote in message
news:A5CAF81E-A63D-42D2-B9E2-4E854138BB5F@microsoft.com...
> I created the HTTPReceive subfolder under the
>  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\BTSSvc.3.0\
> in the registry and then added a Dword entry for HttpBatchSize.
>
> I'm not seeing any change in performance, nor any complaints if I set the
> value to greater than 256.  How can I be sure that the host has isusing
this
> tuning value ?
>

[ Post a follow-up to this message ]

here is what the July release of the docs say.

HttpBatchSize must be defined in
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\BTSSvc.3.0\HttpReceive.

(there are 2 other keys that are instance specific though)



"Christof [MVP]" wrote:

> Are you sure this is the correct location please?
> Isn't this key related to the actual host?  (In that case you might need t
o
> add the GUID somewhere in the regkey path...)  Please double check the
> location since I'm not sure...
>
> Best regards,
> Christof
>
> --
> Christof [Microsoft BizTalk Server MVP]
>
> "Tim B." <TimBur@seattletimes.com> wrote in message
> news:A5CAF81E-A63D-42D2-B9E2-4E854138BB5F@microsoft.com... 
> this 
>
>
>

[ Post a follow-up to this message ]

Hi,

Location:
& #91;HKEY_LOCAL_MACHINE\SYSTEM\CurrentCon
trolSet\Services\BTSS
vc.3.0\HttpReceive]

Entry: "HttpBatchSize"=dword:00000001

I am unsure as to what you are doing exactly, so cannot
assist in how you can tell whether the settings are
taking effect. However, if you write a quick console
application that posts messages to a receive port that
uses the HTTP Adapter then you should be able to tell the
difference between the values easily.

Have you restarted IIS for the settings to take effect?

Matt

>-----Original Message-----
>here is what the July release of the docs say.
>
>HttpBatchSize must be defined in
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\BTSS
vc.3.0\HttpReceive.
>
>(there are 2 other keys that are instance specific
though)
>
>
>
>"Christof [MVP]" wrote:
> 
case you might need to[vbcol=seagreen] 
double check the[vbcol=seagreen] 
4E854138BB5F@microsoft.com...[vbcol=seagreen] 
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\BTSSv
c.3.0\[vbcol=seagreen] 
HttpBatchSize.[vbcol=seagreen] 
complaints if I set the[vbcol=seagreen] 
the host has isusing[vbcol=seagreen] 
>.
>

[ Post a follow-up to this message ]

You probably don't want to set this to 256.  What it does is determine the
maximum batch size to wait on before submitting to BizTalk.  For instance,
if it's set to 10 and 5 documents are received, we'll wait for a bit (not
sure on the wait time,) before submitting them to the engine in hopes that
we'll get to 10.  By setting it to 256 you're telling the engine "if you
get 256 documents via HTTP submit immediately, otherwise wait before
submitting."

Unless you're consistently receiving a large amount of documents over HTTP
there's nothing to gain by setting this to a large value.

You'd need to restart the host that the HTTP adapter runs in to take this
change.  If the host runs across multiple machines you'd want to make the
registry change on all machines that participate in this host.

Larry Franks

This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
--------------------
| Thread-Topic: HTTP Adapter Configuration - HttpBatchSize
| thread-index: AcSJLS/Ov+GY9btgSw2Rej3skrf2SA==
| X-WBNR-Posting-Host: 192.251.219.11
| From: examnotes <TimBur@seattletimes.com>
| Subject: HTTP Adapter Configuration - HttpBatchSize
| Date: Mon, 23 Aug 2004 09:21:04 -0700
| Lines: 8
| Message-ID: <A5CAF81E-A63D-42D2-B9E2-4E854138BB5F@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.1.29
| Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.general:18887
| X-Tomcat-NG: microsoft.public.biztalk.general
|
| I created the HTTPReceive subfolder under the
|  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\BTSSvc.3.0\
| in the registry and then added a Dword entry for HttpBatchSize.
|
| I'm not seeing any change in performance, nor any complaints if I set the
| value to greater than 256.  How can I be sure that the host has isusing
this
| tuning value ?
|
|

[ Post a follow-up to this message ]

Matt,

I hadn't reset IIS, so I tired that, didn't seem to make a difference.

I have a req/res port exposed a webservice, which fires off an orchestraion.
The orchestration uses an req/res http port to commicate with an external
service.

So I had though that for every web service call there would be 4 http posts
to the message box and that I should see an end to end response time change
by adjusting the httpbatchsize parameter.  I set it 1, 256 and (what s/b
illegal) 1000.  There was no difference in the average response times.   I'm
using App Test Center over a 5 minute period with only 1 concurrent conectio
n
to do the testing. I'm assuming that a batch size of 1 would favorably effec
t
the reponse time for this light load situation.

Any ideas ?
Tim

"Matt Hall" wrote:

> Hi,
>
> Location:
> & #91;HKEY_LOCAL_MACHINE\SYSTEM\CurrentCon
trolSet\Services\BTSS
> vc.3.0\HttpReceive]
>
> Entry: "HttpBatchSize"=dword:00000001
>
> I am unsure as to what you are doing exactly, so cannot
> assist in how you can tell whether the settings are
> taking effect. However, if you write a quick console
> application that posts messages to a receive port that
> uses the HTTP Adapter then you should be able to tell the
> difference between the values easily.
>
> Have you restarted IIS for the settings to take effect?
>
> Matt
> 
> vc.3.0\HttpReceive. 
> though) 
> case you might need to 
> double check the 
> 4E854138BB5F@microsoft.com... 
>  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\BTSSv
> c.3.0\ 
> HttpBatchSize. 
> complaints if I set the 
> the host has isusing 
>

[ Post a follow-up to this message ]

Tim, can you try with a simple orchestration that just receives data and
sends a reply?  Let's remove the call out to the external service.  What
I'm wondering is if the process is hitting an average response time due to
internal processing between the receive and the response back to the
calling process.  If we get it down to just the call in and the response
out that should give a cleaner test to see if changing the parameter has
any effect.

Larry Franks

This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
--------------------
| Thread-Topic: HTTP Adapter Configuration - HttpBatchSize
| thread-index: AcSKxUYQN71ruasBSMeDoqe3JJibXA==
| X-WBNR-Posting-Host: 192.251.219.11
| From: examnotes <TimBur@seattletimes.com>
| References:  <A5CAF81E-A63D-42D2-B9E2-4E854138BB5F@microsoft.com>
<uVvHY#TiEHA.1048@tk2msftngp13.phx.gbl>
<7B26F02D-BD33-45D0-A49B-6527C08F47C4@microsoft.com>
<5d9d01c48aab$e19e38a0$a301280a@phx.gbl>
| Subject: Re: HTTP Adapter Configuration - HttpBatchSize
| Date: Wed, 25 Aug 2004 10:02:16 -0700
| Lines: 90
| Message-ID: <8170513C-E841-4B31-A9FB-FB73BAA3C2FD@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.1.29
| Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.general:18990
| X-Tomcat-NG: microsoft.public.biztalk.general
|
| Matt,
|
| I hadn't reset IIS, so I tired that, didn't seem to make a difference.
|
| I have a req/res port exposed a webservice, which fires off an
orchestraion.
|  The orchestration uses an req/res http port to commicate with an
external
| service.
|
| So I had though that for every web service call there would be 4 http
posts
| to the message box and that I should see an end to end response time
change
| by adjusting the httpbatchsize parameter.  I set it 1, 256 and (what s/b
| illegal) 1000.  There was no difference in the average response times.
I'm
| using App Test Center over a 5 minute period with only 1 concurrent
conection
| to do the testing. I'm assuming that a batch size of 1 would favorably
effect
| the reponse time for this light load situation.
|
| Any ideas ?
| Tim
|
| "Matt Hall" wrote:
|
| > Hi,
| >
| > Location:
| > & #91;HKEY_LOCAL_MACHINE\SYSTEM\CurrentCon
trolSet\Services\BTSS
| > vc.3.0\HttpReceive]
| >
| > Entry: "HttpBatchSize"=dword:00000001
| >
| > I am unsure as to what you are doing exactly, so cannot
| > assist in how you can tell whether the settings are
| > taking effect. However, if you write a quick console
| > application that posts messages to a receive port that
| > uses the HTTP Adapter then you should be able to tell the
| > difference between the values easily.
| >
| > Have you restarted IIS for the settings to take effect?
| >
| > Matt
| >
| > >-----Original Message-----
| > >here is what the July release of the docs say.
| > >
| > >HttpBatchSize must be defined in
| > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\BTSS
| > vc.3.0\HttpReceive.
| > >
| > >(there are 2 other keys that are instance specific
| > though)
| > >
| > >
| > >
| > >"Christof [MVP]" wrote:
| > >
| > >> Are you sure this is the correct location please?
| > >> Isn't this key related to the actual host?  (In that
| > case you might need to
| > >> add the GUID somewhere in the regkey path...)  Please
| > double check the
| > >> location since I'm not sure...
| > >>
| > >> Best regards,
| > >> Christof
| > >>
| > >> --
| > >> Christof [Microsoft BizTalk Server MVP]
| > >>
| > >> "Tim B." <TimBur@seattletimes.com> wrote in message
| > >> news:A5CAF81E-A63D-42D2-B9E2-
| > 4E854138BB5F@microsoft.com...
| > >> > I created the HTTPReceive subfolder under the
| > >> >
| >  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\BTSSv
| > c.3.0\
| > >> > in the registry and then added a Dword entry for
| > HttpBatchSize.
| > >> >
| > >> > I'm not seeing any change in performance, nor any
| > complaints if I set the
| > >> > value to greater than 256.  How can I be sure that
| > the host has isusing
| > >> this
| > >> > tuning value ?
| > >> >
| > >>
| > >>
| > >>
| > >.
| > >
| >
|

[ Post a follow-up to this message ]