Web service Performance

[=?Utf-8?B?UGllcnJl?=]

I recently deployed a Web Service (IIS .0 on Windows Server 2003). About 400
clients are using it to synchronize some datas from clients database to web
server database, so they are calling web service methods very often. After a
few hours, the replies from the server are very slow, and I have at the end
osme thread aborted errors generated by my web service.
My first question is : is that better to send 1 query with 10 rows of data
or 10 queries with 1 row of data ??
My second question is : what are the settings to change into web.config to
manage a lot of web service clients ??

[John Saunders]

"Pierre" <Pi****@discuss ions.microsoft. comwrote in message
news:6D******** *************** ***********@mic rosoft.com...

I recently deployed a Web Service (IIS .0 on Windows Server 2003). About
400
clients are using it to synchronize some datas from clients database to
web
server database, so they are calling web service methods very often. After
a
few hours, the replies from the server are very slow, and I have at the
end
osme thread aborted errors generated by my web service.
My first question is : is that better to send 1 query with 10 rows of data
or 10 queries with 1 row of data ??
My second question is : what are the settings to change into web.config to
manage a lot of web service clients ??

The first thing you need to do is find out what the problem is. You have no
way of knowing whether changing the way you send data will make things
better, or worse.
--
John Saunders | MVP - Connected System Developer

[=?Utf-8?B?UGllcnJl?=]

"John Saunders" wrote:

"Pierre" <Pi****@discuss ions.microsoft. comwrote in message
news:6D******** *************** ***********@mic rosoft.com...

I recently deployed a Web Service (IIS .0 on Windows Server 2003). About
400
clients are using it to synchronize some datas from clients database to
web
server database, so they are calling web service methods very often. After
a
few hours, the replies from the server are very slow, and I have at the
end
osme thread aborted errors generated by my web service.
My first question is : is that better to send 1 query with 10 rows of data
or 10 queries with 1 row of data ??
My second question is : what are the settings to change into web.config to
manage a lot of web service clients ??

The first thing you need to do is find out what the problem is. You have no
way of knowing whether changing the way you send data will make things
better, or worse.
--
John Saunders | MVP - Connected System Developer

Hi,
The problem is : on the WebServer the process W3wp.exe is using a lot of
memory, the memory used always increase. after few hours, the server is not
responding, the client call the ws method, and there's no answer from the web
server. In the Web service log message I have a threadAbortExce ption the app
pool. On the server w3wp throw anexception logged in the events viewer : the
request has been aborted (error code 3001) ; exception type : HtpException.
Sometimes after this log I'm finding anoter one which is :ISAPI interface
'C:\WINDOWS\Mic rosoft.NET\Fram ework\v2.0.5072 7\aspnet_isapi. dll' blocked. If
we do a IISRESET, everything is restarting and queries response are going
back quickly to clients (On this pool thre's is just the web service, there's
other pools running).
Find the settings I had in the web.config of the web service :
<httpRuntime executionTimeou t="600" />
And in the machine.config :
<system.web>
<processModel maxWorkerThread s="100" maxIoThreads="1 00"
minWorkerThread s="50"/>
<httpRuntime minFreeThreads= "352" minLocalRequest FreeThreads="30 4"/>
</system.web>

This situation appears about twice a day. When I check in PerfMon the
number of waiting queries increase.

Where can I find the limits of http clients, http queries that IIS can
support, and the settings to optimize into IIS.
I never had this problem when I had about 50 clients connected, but now I
have about 200, and in the near future it will be 500.

Thanks to advice me.
Regards

Pierre