Skip to main content

Programare paralela in .NET 4.0

Plecam de la premiza ca avem o metoda care executa acelasi cod pentru fiecare element dintr-o colectie:
public bool CheckItem(Item item)
{
...
}
In mod natural am scrie:
foreach (Item item in items)
{
item.IsValid = CheckItem(item);
}

sau
items.ForEach(item=>CheckItem(item));
Am putea sa rulam paralel acest cod foarte usor, daca ne folosim de clasa ajutatoare Parallel:
Parallel.ForEach(items,new Action(item=>CheckItem(item)));
O varianta mai simpla in acest caz este sa scriem direct:
Parallel.ForEach(items,CheckItem);
Daca vrem sa parcurgem doar o parte din colectie putem sa scriem in felul urmator:
Parallel.For(0, 3, new Action(index => CheckItem(items[index])));
Atentie, daca lucrati cu stream-uri sau baze de date trebuie avut grija la close si dispose.
Problema este ceea ce se petrece in spate. N threaduri sunt folosite pentru linia de cod scrisa mai sus. Daca suntem pe client side, acest lucru nu este atat de important, dar daca suntem pe partea de server, putem avea mari probleme. De exemplu putem sa ajunge sa avem toate threadurile din pool folosite. Aceasta problema apare din cauza ca pentru fiecare request care vine prin WCF sau HTTP poate sa porneasca N threaduri. Din punct de vedere a scalabilității aici pot sa apara mari problem( vezi P.S. de la sfîrșitul postului).
public async Task CheckItem(ITempDataProvider item)
{
...
}
Task.Factory.ContinueWhenAll(
from item in items select CheckItem(item),
endTask => NotifyWaiter());
Pentru a putea face acest lucru aveti nevoie de Async CTP instalat. Acesta in spate apeleaza asyncron pentru fiecare item in parte metoda CheckItem. Keywordul async ii spune compilatorului ca acesta metoda o sa fie apelata asyncron. Iar ContinueWhenAll creaza un task care o sa fie rulat la sfarsitul executiei listei de taskuri specificate.
Async CTP
O alta varianta este sa folosim
WithDegreeOfParallelism. Aceasta ne permite sa specificam numarul de threaduri care pot sa ruleze paralel prin intermediul limbajului PLINQ
P.S.: Am ajuns sa scriu acest post in momentul in care am scris un cod server side care folosea Parallel.ForEach pentru a prelucra un request de la client si am ajuns doar prin cateva requesturi sa ocup peste 200MB din memorie.

Comments

Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…