Comments on: When to use Async Service Operations http://kennyw.com/indigo/258 Kenny Wolf's Thoughts of the Moment Sat, 11 Oct 2008 00:17:24 +0000 http://wordpress.org/?v=2.2.2 By: WCF and the AsyncPattern property (part 2) « Pedro Félix’s shared memory http://kennyw.com/indigo/258#comment-114406 WCF and the AsyncPattern property (part 2) « Pedro Félix’s shared memory Sat, 28 Jun 2008 13:05:47 +0000 http://kennyw.com/indigo/258#comment-114406 [...] Similarly, Kenny Wolf (from the WCF/WF group) states that If you have an operation that is blocking (accessing SQL, Channels, etc) then you should use AsyncPa... [...] […] Similarly, Kenny Wolf (from the WCF/WF group) states that If you have an operation that is blocking (accessing SQL, Channels, etc) then you should use AsyncPa… […]

]]> By: WCF and the AsyncPattern (part 2) « Pedro Félix’s shared memory http://kennyw.com/indigo/258#comment-114193 WCF and the AsyncPattern (part 2) « Pedro Félix’s shared memory Fri, 27 Jun 2008 13:41:22 +0000 http://kennyw.com/indigo/258#comment-114193 [...] Similarly, Kenny Wolf states that If you have an operation that is blocking (accessing SQL, Channels, etc) then you should use AsyncPa... [...] […] Similarly, Kenny Wolf states that If you have an operation that is blocking (accessing SQL, Channels, etc) then you should use AsyncPa… […]

]]> By: Kenny http://kennyw.com/indigo/258#comment-101270 Kenny Sat, 03 May 2008 18:12:43 +0000 http://kennyw.com/indigo/258#comment-101270 Yes, we do run on IO completion threads by default. And I'm not recommending that you should just call QueueUserWorkItem to get off of the WCF dispatch thread. However, if your work is naturally async (and a Begin/End set of APIs should only be exposed if the API is directly or indirectly using I/O), then you will benefit from using the WCF async pattern. You can calculate pi in a synchronous operation, even if it takes a long time. But if you are holding an idle thread (i.e. calling Thread.Sleep, or out to a database, etc) then you want to let the system reuse the thread that you're on. It's possible that the thread you release will get recycled into the thread that completes your async operation, or maybe not. But either way you want to be concious of system resources and playing nice with the. Yes, we do run on IO completion threads by default. And I’m not recommending that you should just call QueueUserWorkItem to get off of the WCF dispatch thread. However, if your work is naturally async (and a Begin/End set of APIs should only be exposed if the API is directly or indirectly using I/O), then you will benefit from using the WCF async pattern. You can calculate pi in a synchronous operation, even if it takes a long time. But if you are holding an idle thread (i.e. calling Thread.Sleep, or out to a database, etc) then you want to let the system reuse the thread that you’re on. It’s possible that the thread you release will get recycled into the thread that completes your async operation, or maybe not. But either way you want to be concious of system resources and playing nice with the.

]]> By: dominick http://kennyw.com/indigo/258#comment-100705 dominick Thu, 01 May 2008 19:26:20 +0000 http://kennyw.com/indigo/258#comment-100705 sorry - i meant 1000 IO threads. sorry - i meant 1000 IO threads.

]]> By: dominick http://kennyw.com/indigo/258#comment-100387 dominick Wed, 30 Apr 2008 04:55:32 +0000 http://kennyw.com/indigo/258#comment-100387 Hi Kenny, my understanding was that WCF requests already run on IO completion port threads (IO thread pool) which already have the characteristics to optimize work when waiting for IO. In ASP.NET you typically use async handler to free up a worker thread (and dispatch to an IO thread instead). But worker threads are a very sparse resource - whereas WCF has 100 IO threads by default. So I wonder what's the benefit in WCF using async pattern? On which thread pool does the async work end up? cheers, dominick Hi Kenny,

my understanding was that WCF requests already run on IO completion port threads (IO thread pool) which already have the characteristics to optimize work when waiting for IO.

In ASP.NET you typically use async handler to free up a worker thread (and dispatch to an IO thread instead). But worker threads are a very sparse resource - whereas WCF has 100 IO threads by default.

So I wonder what’s the benefit in WCF using async pattern? On which thread pool does the async work end up?

cheers,
dominick

]]>