Skip to main content

Guid.Comb

In ultimele zile am început sa lucrez cu Fluent NHibernate si am descoperit GuidComb. M-am documentat sa vad ce înseamna de fapt. Pe scurt:
One of the better alternatives that i kinda like is the guid.comb strategy. Using regular guids as a primary key value leads to fragmented indexes (due to the randomness of the guid’s value) which leads to bad performance. This is a problem that the guid.comb strategy can solve quite easily for you.
Nu are rost sa traduc și să explic din nou acelasi lucru. O să găsiți pe Google destule materiale. Partea interesanta este modul in care se generează aceste guiduri.
Din cei 32 de biti pe care un guid ii conține, 16 sunt generați in funcție de configurația hardware a mașinii( începînd cu Windows 2000, seria plăcii de rețea nu se mai folosește).
Iar următorii 16 sunt generați in forma următoare:
  • 0-9: se generează pe baza unui uniqueidentifier( depinde de framework);
  • 10-15: pe baza la Datetime;
Acesta este un algoritm de generate de Guid destul de simplu si care isi face treaba foarte bine cînd avem de lucru cu DB. Este foarte folositor mai ales cand trebe sa generam PK. Începînd de la Sql Server 2005 exista Sequential Guid care ii foarte asemănător.
In general se cîștiga un spor de performanta de 25%-30% pe tabele care conține PK ca și guid.In cazul in care tabela pe care lucrați nu are PK, sporul de performanta poate sa fie 0% sau chiar negativ in unele situații. Pentru mai multe informații despre sporul de performanta puteti sa gasiti aici.

PS: Cînd ne ajuta un Guid? Un exemplu este cînd se lucrează cu o aplicația și offline, caz in care la sincronizare nu mai este nevoie de regenerare de PK.

Comments

  1. Se pare ca pierderea de performanta e numai daca acel PK are un clustered index, altfel nu.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…