How can MVC website benefit from the new parallelism features in .net 4? don’t websites support parallelism by default since multiple users access them at the same time? Can someone clarify this?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How can MVC website benefit from the new parallelism features in .net 4? don’t websites support parallelism by default since multiple users access them at the same time? Can someone clarify this?
Executing tasks in parallel is especially useful for long running tasks. What constitutes a long running task might differ, but it should be longer than the overhead of spinning up and synchronizing the threads.
So, there is no particular benefit for MVC, but there is a general benefit for each request which require more things to be run in parallel.
There’s an article from 2007 in MSDN Magazine which outlines some performance aspects of the parallel library.
Example 1: a user hits a page which displays two different graphs. Each graph is calculated from a dataset. Executing the calculations in parallel will benefit the overall time to render the page. (Executing parallel individual tasks)
Example 2: You need to execute some function on a list of data, And use
Parallel.Forto enumerate over the data and execute some code on it in parallel.You should analyze your application and figure out which parts can be run in parallel, and then test with the new language features if it helps your application or not.