I want to apply this type of argument in my asp-net-mvc application:
User ->
The server executes some time-consuming arguments in ~ 15 threads (I get data from really slow independent sources) ->
When all the work is done, the server merges into the result and sends it back to the user the other day I have a Seen the article, in which It has been explained why the ASP is creating a new thread- the NET application is not highly recommended, and ThreadPool is the one that should be used. What are the best practices for MVC in this case? Why do not I use my threads, backgroundwalkers, tasks, whatever I make and use Threadpool? If this is the case, then it will be hosted on a public server.
If you are using Net 4, I would also recommend looking at parallel namespaces, they make it even easier and do a better job using all your CPU cores.
I will also see offloading completely from my main web app, to handle this long-standing request or to have a different set of message queues, you can scale it much more easily. And your web app will be allowed to worry about the servicing page, something like "Iis long-lasting requests" to get started
Comments
Post a Comment