task-parallel-library

问题 I have three methods that I call to do some number crunching that are as follows results.LeftFront.CalcAi(); results.RightFront.CalcAi(); results.RearSuspension.CalcAi(geom, vehDef.Geometry.LTa.TaStiffness, vehDef.Geometry.RTa.TaStiffness); Each of the functions is independent of each other and can be computed in parallel with no dead locks. What is the easiest way to compute these in parallel without the containing method finishing until all three are done? 回答1: See the TPL documentation.

问题 I have three methods that I call to do some number crunching that are as follows results.LeftFront.CalcAi(); results.RightFront.CalcAi(); results.RearSuspension.CalcAi(geom, vehDef.Geometry.LTa.TaStiffness, vehDef.Geometry.RTa.TaStiffness); Each of the functions is independent of each other and can be computed in parallel with no dead locks. What is the easiest way to compute these in parallel without the containing method finishing until all three are done? 回答1: See the TPL documentation.

问题 I have three methods that I call to do some number crunching that are as follows results.LeftFront.CalcAi(); results.RightFront.CalcAi(); results.RearSuspension.CalcAi(geom, vehDef.Geometry.LTa.TaStiffness, vehDef.Geometry.RTa.TaStiffness); Each of the functions is independent of each other and can be computed in parallel with no dead locks. What is the easiest way to compute these in parallel without the containing method finishing until all three are done? 回答1: See the TPL documentation.

问题 I am new to threading and parallel library. I am trying to understand the MaxDegreeOfParallelism and to what value it should be set. Done some reading and to me might be a bit misleading. If I want to run on 4 threads I thought I could do var parOptions=new ParallelOptions(); parOptions.MaxDegreeOfParallelism=4; However doing some more reading it looks like that in my case 4 does not mean runs on 4 threads but is more todo with Cores and how much it uses. To keep it simple what is the correct

问题 This is kind of follow up to one of my earlier question here. In summary I am trying to come up with a lock free design for this scenario where I upon cancellation of task I want to call a method of third party library. In response to my question, a helpful SO participant suggested to use CancellationToken.Register but I am not sure where and how can I use that here. Below is code that I come up with. Please let me know if you see any issue with this approach or if there are any better

问题 I have a view model that is fetching a row of records and displaying on the Windows phone UI.. This view model method which fetches the data is doing a lot of Tasks, all marked with Await operations.. Looks like below: async Task GetData() { var dataCollection = await GetSomeData(); await DoThis(); await DoThat(); } The UI refreshes after the 'DoThis' call is invoked. Now I just observed that if I introduce a Task.Delay in the code before other Tasks are done, the UI is refreshed immediately.

问题 Why does this test fail? The only difference between t1 and t2 , as far as I can tell, is that t1 is a Task , and t2 is a Task<int> . Yet for some reason t2 ends up in the Faulted status, as opposed to the Canceled status. Why would the behavior differ? [Test] public void Test_foo() { var t1 = Task.Run(() => { throw new OperationCanceledException(); }); try { t1.Wait(); } catch (AggregateException e) { Assert.IsTrue(t1.IsCanceled); } var t2 = Task.Run(() => { throw new

问题 I was wondering if it is possible to call a number of different stored procedures with the same parameters asynchronously by using tasks and then waiting for all the results to return. I have the following: private Task<DataTable> DataBaseCall(string procedureName, params Pair[] where) { DataTable data = new DataTable(); SqlConnection connection = new SqlConnection(connStr); SqlCommand command = new SqlCommand(procedureName, connection); connection.Open(); for (int i = 0; i < where.Length; i+

问题 I'm building a .NET 4.0 application that uses ADO.NET, so I cannot use async/await. I don't want a solution for that, but I do want to know what of the following implementations is best and why. My unit tests pass for all three implementations, but I want to know the difference between these three. #1 Nesting tasks In my first implementation I wrap a task in another task. I think spinning up two tasks is bad for performance, but I'm not sure. public virtual Task<IDataReader>

问题 I am trying to understand the usage of async await and i studied few blog posts and now i have made a testing code but it is not working the way i am expecting it to work. I have a method which returns List: private List<Employee> GetEmployees() { IList<Employee> list = new List<Employee>(); list.Add(new Employee() { Id = 1, Age = 20, Name = "Kavin" }); list.Add(new Employee() { Id = 2, Age = 30, Name = "Alen" }); list.Add(new Employee() { Id = 3, Age = 20, Name = "Suresh" }); list.Add(new