| Groups | Blog | Home |
dotnet remoting : Asynchronous Remoting and its effects on ASP.NET Threading
Now I know that we can call .NET remoting components asynchronously from ASP.NET pages and it works like a charm! But I am concerned about the behavior of the overall system in this case and how does ASP.NET handle threads. (1) Lets say I asynchronously call .NET remoting component and redirects user to a page. What happens to the ASP.NET thread that called the remoting component asynchronously? Does that thread get stuck until the call actually completes or the thread aborts as soon as the HTTP request is completed? (2) What if I pass null in the last two parameters (AsyncCalback and object) of the delegate BeginInvoke method? I tried passing null in last two parameters of the BeginInvoke call and it works fine! What I am trying to figure out for sure is the "threading behavior" in case of making asynchronous calls from ASP.NET pages because I don't want to do anything that might affect the server threading because the application I am working is supposed to be hit by thousands of users and scalability is a big issues for me! Could you guys pls answer the above questions and throw some light on the ASP.NET threading and its behavior in case of asynchronous remoting. Thanks,
ASP.NET handles threading the usual way. A thread from the pool is used to
handle the request. A call, any call, executes the calling code. Asynchronous calls return immediately, the called asynchronous code fires on its own thread. The caller - main thread - moves on. For asynchronous calls with callbacks, if there is nothing to call back to, nothing happens. You have to be careful with callbacks and delegates because by the time these calls get executed, the context may not be around resulting in a null reference exception. -- Regards, Alvin Bruney - ASP.NET MVP [Shameless Author Plug] The Microsoft Office Web Components Black Book with .NET Now available @ www.lulu.com/owc, Amazon.com etc [quoted text, click to view] "Stewart Rogers" <StewartRogers@discussions.microsoft.com> wrote in message news:2C8E52BD-6E96-4CF9-A566-3E26E6257ED4@microsoft.com... > Hi all, > Now I know that we can call .NET remoting components asynchronously from > ASP.NET pages and it works like a charm! But I am concerned about the > behavior of the overall system in this case and how does ASP.NET handle > threads. > > (1) Lets say I asynchronously call .NET remoting component and redirects > user to a page. What happens to the ASP.NET thread that called the > remoting > component asynchronously? Does that thread get stuck until the call > actually > completes or the thread aborts as soon as the HTTP request is completed? > > (2) What if I pass null in the last two parameters (AsyncCalback and > object) > of the delegate BeginInvoke method? > > I tried passing null in last two parameters of the BeginInvoke call and it > works fine! > > What I am trying to figure out for sure is the "threading behavior" in > case > of making asynchronous calls from ASP.NET pages because I don't want to do > anything that might affect the server threading because the application I > am > working is supposed to be hit by thousands of users and scalability is a > big > issues for me! > > Could you guys pls answer the above questions and throw some light on the > ASP.NET threading and its behavior in case of asynchronous remoting. > > Thanks, > Stewart Rogers
Thanks for your response Alvin but I still have some questions, mostly
regarding threading. (1) Looks like there will be two different thread pools involved when using remoting in ASP.NET. One pool would be ASP.NET worker thread pool whereas the other one would be .NET remoting thread pool. am I right? (2) I understand that ASP.NET uses worker threads to service the HTTP request and that thread comes from ASP.NET's own pool of threads. Is that thread returned to the ASP.NET worker thread pool after dispatching the asynchronous call? (3) You said that "the called asynchronous code fires on its own thread". Who supplies that thread? ASP.NET worker thread pool or the .NET remoting thread pool? (4) You said that "The caller - main thread - moves on". I think you are referring to the ASP.NET worker thread that invoked the component. am I right? (5) You said "For asynchronous calls with callbacks, if there is nothing to call back to, nothing happens". That means if I pass null in both of the parameters to BeginInvoke call then I should be ok. Any thoughts? I know these are quite a few questions to answer but a through/detailed reply will help me understand the threading behavior. Thanks for your all of your help; I highly appreciate that. Stewart [quoted text, click to view] "Alvin Bruney [MVP - ASP.NET]" wrote:
> ASP.NET handles threading the usual way. A thread from the pool is used to > handle the request. A call, any call, executes the calling code. > Asynchronous calls return immediately, the called asynchronous code fires on > its own thread. The caller - main thread - moves on. For asynchronous calls > with callbacks, if there is nothing to call back to, nothing happens. You > have to be careful with callbacks and delegates because by the time these > calls get executed, the context may not be around resulting in a null > reference exception. > > -- > Regards, > Alvin Bruney - ASP.NET MVP > > [Shameless Author Plug] > The Microsoft Office Web Components Black Book with .NET > Now available @ www.lulu.com/owc, Amazon.com etc > "Stewart Rogers" <StewartRogers@discussions.microsoft.com> wrote in message > news:2C8E52BD-6E96-4CF9-A566-3E26E6257ED4@microsoft.com... > > Hi all, > > Now I know that we can call .NET remoting components asynchronously from > > ASP.NET pages and it works like a charm! But I am concerned about the > > behavior of the overall system in this case and how does ASP.NET handle > > threads. > > > > (1) Lets say I asynchronously call .NET remoting component and redirects > > user to a page. What happens to the ASP.NET thread that called the > > remoting > > component asynchronously? Does that thread get stuck until the call > > actually > > completes or the thread aborts as soon as the HTTP request is completed? > > > > (2) What if I pass null in the last two parameters (AsyncCalback and > > object) > > of the delegate BeginInvoke method? > > > > I tried passing null in last two parameters of the BeginInvoke call and it > > works fine! > > > > What I am trying to figure out for sure is the "threading behavior" in > > case > > of making asynchronous calls from ASP.NET pages because I don't want to do > > anything that might affect the server threading because the application I > > am > > working is supposed to be hit by thousands of users and scalability is a > > big > > issues for me! > > > > Could you guys pls answer the above questions and throw some light on the > > ASP.NET threading and its behavior in case of asynchronous remoting. > > > > Thanks, > > Stewart Rogers > >
1. not exactly, both pools are actually the same pool. there are 25 worker
threads for asp.net and 25 more for IO related activities. That's it. There aren't anymore available. 2. yes. the beauty of the thread pool is that once a queued item is thru servicing, it returns back to the pool. 3. see 1. 4. yes. call execution occurs sequentially from the main thread's perspective. If the sequential call fires an asynchronous object, it simple returns. the async object then executes on its own thread. If the object is not an async object, then the main thread waits for the completion of the call. 5. Yup. that's right. Quoting the docs: An array of type Object to pass as arguments to the given method. This can be a null reference (Nothing in Visual Basic) if no arguments are needed. -- Regards, Alvin Bruney - ASP.NET MVP [Shameless Author Plug] The Microsoft Office Web Components Black Book with .NET Now available @ www.lulu.com/owc, Amazon.com etc [quoted text, click to view] "Stewart Rogers" <StewartRogers@discussions.microsoft.com> wrote in message news:51626805-D7F6-4D10-9288-DD983F5F49EA@microsoft.com... > Thanks for your response Alvin but I still have some questions, mostly > regarding threading. > > (1) Looks like there will be two different thread pools involved when > using > remoting in ASP.NET. One pool would be ASP.NET worker thread pool whereas > the > other one would be .NET remoting thread pool. am I right? > > (2) I understand that ASP.NET uses worker threads to service the HTTP > request and that thread comes from ASP.NET's own pool of threads. Is that > thread returned to the ASP.NET worker thread pool after dispatching the > asynchronous call? > > (3) You said that "the called asynchronous code fires on its own thread". > Who supplies that thread? ASP.NET worker thread pool or the .NET remoting > thread pool? > > (4) You said that "The caller - main thread - moves on". I think you are > referring to the ASP.NET worker thread that invoked the component. am I > right? > > (5) You said "For asynchronous calls with callbacks, if there is nothing > to > call back to, nothing happens". That means if I pass null in both of the > parameters to BeginInvoke call then I should be ok. Any thoughts? > > I know these are quite a few questions to answer but a through/detailed > reply will help me understand the threading behavior. > > Thanks for your all of your help; I highly appreciate that. > > Stewart > > "Alvin Bruney [MVP - ASP.NET]" wrote: > >> ASP.NET handles threading the usual way. A thread from the pool is used >> to >> handle the request. A call, any call, executes the calling code. >> Asynchronous calls return immediately, the called asynchronous code fires >> on >> its own thread. The caller - main thread - moves on. For asynchronous >> calls >> with callbacks, if there is nothing to call back to, nothing happens. You >> have to be careful with callbacks and delegates because by the time these >> calls get executed, the context may not be around resulting in a null >> reference exception. >> >> -- >> Regards, >> Alvin Bruney - ASP.NET MVP >> >> [Shameless Author Plug] >> The Microsoft Office Web Components Black Book with .NET >> Now available @ www.lulu.com/owc, Amazon.com etc >> "Stewart Rogers" <StewartRogers@discussions.microsoft.com> wrote in >> message >> news:2C8E52BD-6E96-4CF9-A566-3E26E6257ED4@microsoft.com... >> > Hi all, >> > Now I know that we can call .NET remoting components asynchronously >> > from >> > ASP.NET pages and it works like a charm! But I am concerned about the >> > behavior of the overall system in this case and how does ASP.NET handle >> > threads. >> > >> > (1) Lets say I asynchronously call .NET remoting component and >> > redirects >> > user to a page. What happens to the ASP.NET thread that called the >> > remoting >> > component asynchronously? Does that thread get stuck until the call >> > actually >> > completes or the thread aborts as soon as the HTTP request is >> > completed? >> > >> > (2) What if I pass null in the last two parameters (AsyncCalback and >> > object) >> > of the delegate BeginInvoke method? >> > >> > I tried passing null in last two parameters of the BeginInvoke call and >> > it >> > works fine! >> > >> > What I am trying to figure out for sure is the "threading behavior" in >> > case >> > of making asynchronous calls from ASP.NET pages because I don't want to >> > do >> > anything that might affect the server threading because the application >> > I >> > am >> > working is supposed to be hit by thousands of users and scalability is >> > a >> > big >> > issues for me! >> > >> > Could you guys pls answer the above questions and throw some light on >> > the >> > ASP.NET threading and its behavior in case of asynchronous remoting. >> > >> > Thanks, >> > Stewart Rogers >> >> >>
you just need to be careful that you don't starve the threadpool by too many
asynchronous calls. Everything async uses a thread from the thread pool. ice [quoted text, click to view] "Alvin Bruney [MVP - ASP.NET]" <www.lulu.com/owc> wrote in message news:#PMlDqDUFHA.544@TK2MSFTNGP15.phx.gbl... > 1. not exactly, both pools are actually the same pool. there are 25 worker > threads for asp.net and 25 more for IO related activities. That's it. There > aren't anymore available. > > 2. yes. the beauty of the thread pool is that once a queued item is thru > servicing, it returns back to the pool. > > 3. see 1. > > 4. yes. call execution occurs sequentially from the main thread's > perspective. If the sequential call fires an asynchronous object, it simple > returns. the async object then executes on its own thread. If the object is > not an async object, then the main thread waits for the completion of the > call. > > > 5. Yup. that's right. > Quoting the docs: > An array of type Object to pass as arguments to the given method. This can > be a null reference (Nothing in Visual Basic) if no arguments are needed. > > > > -- > Regards, > Alvin Bruney - ASP.NET MVP > > [Shameless Author Plug] > The Microsoft Office Web Components Black Book with .NET > Now available @ www.lulu.com/owc, Amazon.com etc > "Stewart Rogers" <StewartRogers@discussions.microsoft.com> wrote in message > news:51626805-D7F6-4D10-9288-DD983F5F49EA@microsoft.com... > > Thanks for your response Alvin but I still have some questions, mostly > > regarding threading. > > > > (1) Looks like there will be two different thread pools involved when > > using > > remoting in ASP.NET. One pool would be ASP.NET worker thread pool whereas > > the > > other one would be .NET remoting thread pool. am I right? > > > > (2) I understand that ASP.NET uses worker threads to service the HTTP > > request and that thread comes from ASP.NET's own pool of threads. Is that > > thread returned to the ASP.NET worker thread pool after dispatching the > > asynchronous call? > > > > (3) You said that "the called asynchronous code fires on its own thread". > > Who supplies that thread? ASP.NET worker thread pool or the .NET remoting > > thread pool? > > > > (4) You said that "The caller - main thread - moves on". I think you are > > referring to the ASP.NET worker thread that invoked the component. am I > > right? > > > > (5) You said "For asynchronous calls with callbacks, if there is nothing > > to > > call back to, nothing happens". That means if I pass null in both of the > > parameters to BeginInvoke call then I should be ok. Any thoughts? > > > > I know these are quite a few questions to answer but a through/detailed > > reply will help me understand the threading behavior. > > > > Thanks for your all of your help; I highly appreciate that. > > > > Stewart > > > > "Alvin Bruney [MVP - ASP.NET]" wrote: > > > >> ASP.NET handles threading the usual way. A thread from the pool is used > >> to > >> handle the request. A call, any call, executes the calling code. > >> Asynchronous calls return immediately, the called asynchronous code fires > >> on > >> its own thread. The caller - main thread - moves on. For asynchronous > >> calls > >> with callbacks, if there is nothing to call back to, nothing happens. You > >> have to be careful with callbacks and delegates because by the time these > >> calls get executed, the context may not be around resulting in a null > >> reference exception. > >> > >> -- > >> Regards, > >> Alvin Bruney - ASP.NET MVP > >> > >> [Shameless Author Plug] > >> The Microsoft Office Web Components Black Book with .NET > >> Now available @ www.lulu.com/owc, Amazon.com etc > >> "Stewart Rogers" <StewartRogers@discussions.microsoft.com> wrote in > >> message > >> news:2C8E52BD-6E96-4CF9-A566-3E26E6257ED4@microsoft.com... > >> > Hi all, > >> > Now I know that we can call .NET remoting components asynchronously > >> > from > >> > ASP.NET pages and it works like a charm! But I am concerned about the > >> > behavior of the overall system in this case and how does ASP.NET handle > >> > threads. > >> > > >> > (1) Lets say I asynchronously call .NET remoting component and > >> > redirects > >> > user to a page. What happens to the ASP.NET thread that called the > >> > remoting > >> > component asynchronously? Does that thread get stuck until the call > >> > actually > >> > completes or the thread aborts as soon as the HTTP request is > >> > completed? > >> > > >> > (2) What if I pass null in the last two parameters (AsyncCalback and > >> > object) > >> > of the delegate BeginInvoke method? > >> > > >> > I tried passing null in last two parameters of the BeginInvoke call and > >> > it > >> > works fine! > >> > > >> > What I am trying to figure out for sure is the "threading behavior" in > >> > case > >> > of making asynchronous calls from ASP.NET pages because I don't want to > >> > do > >> > anything that might affect the server threading because the application > >> > I > >> > am > >> > working is supposed to be hit by thousands of users and scalability is > >> > a > >> > big > >> > issues for me! > >> > > >> > Could you guys pls answer the above questions and throw some light on > >> > the > >> > ASP.NET threading and its behavior in case of asynchronous remoting. > >> > > >> > Thanks, > >> > Stewart Rogers > >> > >> > >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
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 |