What are some helpful tips for building multi-core, optimized ASP.NET MVC applications?

I see a lot of multicore information on the Internet applied to desktop applications, but I wonder: what tips and pointers will be useful for ASP.NET MVC web developers creating applications that use most of the multiple cores / processors?

+4
source share
3 answers

Leave it on the web server

I would not bother with it in a web application if it does not handle some kind of heavy processor processing. Make sure that your application works well and leave the use of processor (s) on the web server to serve requests with all the kernels in the system.

+2
source

If you have several long processes per request, you can parallelize them. But overall itโ€™s not worth the coding effort and errors that may appear.

In practice, just make each request more accurate, and then you can process more requests at a time.

+1
source

I don't think the web application gets the same value from multi-core / multi-threaded applications as the desktop application, because ultimately every HTTP request is synchronous (except for AJAX, but every AJAX request is still HTTP request), Of course, a server with a multi-core processor is good, and probably it can process requests faster, but I donโ€™t think that there is much (in general) you can do with a multi-threaded application that ultimately displays an HTML document .

0
source

All Articles