Geek asks and answers

ASP.NET async / wait part 2

I have a variation of the benefits of async / await-on-ASP.NET from this question .

I understand that asynchrony is not the same as parallelism. So, on the web server, I wonder how many benefits of async / await brings to ASP.NET pages.

Is IIS + ASP.NET not very well allocated threads for requests, and if the onen page is busy waiting for a resource, the server will simply switch to processing another request that should work?

There is a limited number of threads in the pool for ASP.NET - do they use them more efficiently asynchronously?

As Mr. Skeet said, answering the question above, we are not talking about blocking the user interface flow. We are already multi-threaded, and the web response cannot be completed until all query tasks are completed, asynchronous or not, right?

I think it boils down to the following:

Is there any benefit from reading the resource asynchronously (say, a file or a database query) on an ASP.NET page and blocking it?

+5
source share
1 answer

If one page is busy waiting for a resource, will the server simply switch to processing another request that should work?

I do not think so. I would be very surprised if this were so. It is theoretically possible, but very difficult.

ASP.NET - ?

, await -, .

- , , , ?

. async - .

- (, ) ASP.NET ?

!

//db, . await / /db, .

( !) , , () , , ! Zero-threaded concurrency, .

, await - (, ) .

: async , , .

: intro to async post this .

+8

More articles:


All Articles