2
I’m doing a project in ASP.NET MVC + IIS and realized that when making a request to a page with long reading in the Database (using Entity Framework), if I open another window and try to access any other page of the site (the Home for example, which has no reading and should open quickly), this second request ends up waiting for the first to finish to then display the page.
I’m worried about this type of blocking, because when the site is in production it may end up blocking the request of customers and even generating a timeout.
I don’t know if this is some kind of configuration that should be inserted into the IIS or the application.
If anyone can help me with the following question, thank you.
PS: I’m not using asynchronous methods in Controllers. I believe that the asynchronous method would only avoid freezing the screen for the user, but it does not interfere with blocking the requests of other clients, but as I do not have much knowledge in asynchronous programming, if I am wrong correct me.
Perfect guy, I think this question will help a lot of people too. I thank you for the answer.
– Wilson Santos