AsyncAwait a WCF Call

Question

I have a MVC4 Application which waits for a third party subsystem. Each request takes 2 to 5 Seconds. The communication is done via WCF and i use NET 4.5.

Currently i wait synchronous to the answer and show then results. All sql queries after the result is received cannot be moved in between the async and await, as they are depended on the result.

Does it make sense anyway to apply the AsyncAwait pattern?

Does it reduce the amount of threads inside the IIS?

Sample:

client2 = new ServiceReference2.Service1Client(); string res = await client2.GetHello2Async();

Example of proxy can be viewed in guruumeditation.net/async-await-with-wcf — Michael Freidgeim
– Michael Freidgeim, Commented Jul 27, 2013 at 6:25
thx. i know. my question was less how, more if it makes sense if i do nothing between the request is running. — NickD
– NickD, Commented Jul 27, 2013 at 7:43

svick · Accepted Answer · 2013-06-10 14:22:39Z

1

Yes, switching to async-await is going to decrease the number of ThreadPool threads used by your code. That's the primary reason for using async-await in server-side applications.

edited Jun 10, 2013 at 14:22

answered Jun 10, 2013 at 13:00

svick

247k54 gold badges405 silver badges535 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

svick Over a year ago

@PauloMorgado Your suggested edit is wrong. There is no special “request handling thread pool”, in ASP.NET, there is just the single ThreadPool.

Collectives™ on Stack Overflow

AsyncAwait a WCF Call

1 Answer 1

1 Comment

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Related