|
|
You're in the
dotnet web services
group:multi tasking?
dotnet web services:
Strictly as an example, suppose I write a web service that takes an
employee number and then does some processing and returns their security clearance, name, department or some such stuff. Again for arguments sake say this processing takings about 15 seconds each time. Lastly assume there are lots of people making inquiries via this web service and at some times of the day we get a request every 2 or 3 seconds. Can a web service start a new request if it hasn't finished the previous one? Is it multi-tasking or multi-threaded by nature or is there something I need to do to allow it to do this? The object is nobody should have to wait for a previous request to finish for their request to start.
[quoted text, click to view]
"cj" <cj@nospam.nospam> wrote in message news:%23COKHb5XIHA.4896@TK2MSFTNGP06.phx.gbl... > Strictly as an example, suppose I write a web service that takes an > employee number and then does some processing and returns their security > clearance, name, department or some such stuff. Again for arguments sake > say this processing takings about 15 seconds each time. Lastly assume > there are lots of people making inquiries via this web service and at some > times of the day we get a request every 2 or 3 seconds. Can a web service > start a new request if it hasn't finished the previous one? Is it > multi-tasking or multi-threaded by nature or is there something I need to > do to allow it to do this? The object is nobody should have to wait for a > previous request to finish for their request to start. ASP.NET will start a new worker thread per request. -- -------------------------------------------------------------------------------- John Saunders | MVP - Windows Server System - Connected System Developer
Excellent. I had hoped it would. Now bear with me a minute. If part
of the processing is to make a sql connection and look up data, I'd assume that each thread would make it's own connection--correct? [quoted text, click to view] John Saunders [MVP] wrote:
> "cj" <cj@nospam.nospam> wrote in message > news:%23COKHb5XIHA.4896@TK2MSFTNGP06.phx.gbl... >> Strictly as an example, suppose I write a web service that takes an >> employee number and then does some processing and returns their security >> clearance, name, department or some such stuff. Again for arguments sake >> say this processing takings about 15 seconds each time. Lastly assume >> there are lots of people making inquiries via this web service and at some >> times of the day we get a request every 2 or 3 seconds. Can a web service >> start a new request if it hasn't finished the previous one? Is it >> multi-tasking or multi-threaded by nature or is there something I need to >> do to allow it to do this? The object is nobody should have to wait for a >> previous request to finish for their request to start. >
cj <cj@nospam.nospam> wrote in news:Ov$krh5XIHA.4684@TK2MSFTNGP06.phx.gbl:
[quoted text, click to view] > Excellent. I had hoped it would. Now bear with me a minute. If part > of the processing is to make a sql connection and look up data, I'd > assume that each thread would make it's own connection--correct? Correct - each web service connection will request a new sql connection from the sql connection pool. However, you could use child threads to increase concurrency - but depending on your application, the performance may or may not increase. --
just remember though, somewhere everything has to add up or you will run out
of one resource or another. having the web app run multi-threaded so users don't have to wait for it is fine, but if each query still takes 15 seconds from the database it has to be able to handle the multiple simultaneous requests also. if the database server can't handle a request every 2 or 3 seconds eventually you will not be able to connect, it will crash, or something else bad will happen. [quoted text, click to view] "cj" <cj@nospam.nospam> wrote in message news:Ov$krh5XIHA.4684@TK2MSFTNGP06.phx.gbl... > Excellent. I had hoped it would. Now bear with me a minute. If part of > the processing is to make a sql connection and look up data, I'd assume > that each thread would make it's own connection--correct? > > > John Saunders [MVP] wrote: >> "cj" <cj@nospam.nospam> wrote in message >> news:%23COKHb5XIHA.4896@TK2MSFTNGP06.phx.gbl... >>> Strictly as an example, suppose I write a web service that takes an >>> employee number and then does some processing and returns their security >>> clearance, name, department or some such stuff. Again for arguments >>> sake say this processing takings about 15 seconds each time. Lastly >>> assume there are lots of people making inquiries via this web service >>> and at some times of the day we get a request every 2 or 3 seconds. Can >>> a web service start a new request if it hasn't finished the previous >>> one? Is it multi-tasking or multi-threaded by nature or is there >>> something I need to do to allow it to do this? The object is nobody >>> should have to wait for a previous request to finish for their request >>> to start. >> >> ASP.NET will start a new worker thread per request.
This is just an example.
[quoted text, click to view] Dave wrote:
> just remember though, somewhere everything has to add up or you will run out > of one resource or another. having the web app run multi-threaded so users > don't have to wait for it is fine, but if each query still takes 15 seconds > from the database it has to be able to handle the multiple simultaneous > requests also. if the database server can't handle a request every 2 or 3 > seconds eventually you will not be able to connect, it will crash, or > something else bad will happen. > > "cj" <cj@nospam.nospam> wrote in message > news:Ov$krh5XIHA.4684@TK2MSFTNGP06.phx.gbl... >> Excellent. I had hoped it would. Now bear with me a minute. If part of >> the processing is to make a sql connection and look up data, I'd assume >> that each thread would make it's own connection--correct? >> >> >> John Saunders [MVP] wrote: >>> "cj" <cj@nospam.nospam> wrote in message >>> news:%23COKHb5XIHA.4896@TK2MSFTNGP06.phx.gbl... >>>> Strictly as an example, suppose I write a web service that takes an >>>> employee number and then does some processing and returns their security >>>> clearance, name, department or some such stuff. Again for arguments >>>> sake say this processing takings about 15 seconds each time. Lastly >>>> assume there are lots of people making inquiries via this web service >>>> and at some times of the day we get a request every 2 or 3 seconds. Can >>>> a web service start a new request if it hasn't finished the previous >>>> one? Is it multi-tasking or multi-threaded by nature or is there >>>> something I need to do to allow it to do this? The object is nobody >>>> should have to wait for a previous request to finish for their request >>>> to start. >>> ASP.NET will start a new worker thread per request. >
Hi Cj,
ASP.NET webservice use the same threading model as ASP.NET webform application. ASP.NET runtime pickup a worker thread from .NET clr threadpool to process each comming request and release it back to the pool after finishs the request. Here is a very good reference about ASP.NET threading model: #Microsoft ASP.NET Threading http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/en/tra nscripts/wct060503.asp Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- Date: Sat, 26 Jan 2008 23:31:12 -0500 From: cj <cj@nospam.nospam> User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 Subject: Re: multi tasking? This is just an example. [quoted text, click to view] Dave wrote:
> just remember though, somewhere everything has to add up or you will run out > of one resource or another. having the web app run multi-threaded so users > don't have to wait for it is fine, but if each query still takes 15 seconds > from the database it has to be able to handle the multiple simultaneous > requests also. if the database server can't handle a request every 2 or 3 > seconds eventually you will not be able to connect, it will crash, or > something else bad will happen. > > "cj" <cj@nospam.nospam> wrote in message > news:Ov$krh5XIHA.4684@TK2MSFTNGP06.phx.gbl... >> Excellent. I had hoped it would. Now bear with me a minute. If part of >> the processing is to make a sql connection and look up data, I'd assume >> that each thread would make it's own connection--correct? >> >> >> John Saunders [MVP] wrote: >>> "cj" <cj@nospam.nospam> wrote in message >>> news:%23COKHb5XIHA.4896@TK2MSFTNGP06.phx.gbl... >>>> Strictly as an example, suppose I write a web service that takes an >>>> employee number and then does some processing and returns their security >>>> clearance, name, department or some such stuff. Again for arguments >>>> sake say this processing takings about 15 seconds each time. Lastly >>>> assume there are lots of people making inquiries via this web service >>>> and at some times of the day we get a request every 2 or 3 seconds. Can >>>> a web service start a new request if it hasn't finished the previous >>>> one? Is it multi-tasking or multi-threaded by nature or is there >>>> something I need to do to allow it to do this? The object is nobody >>>> should have to wait for a previous request to finish for their request >>>> to start. >>> ASP.NET will start a new worker thread per request. >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |