Skip to main content

Guid.Comb

By
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.
Labels:

Comments

  1. IoanAugust 13, 2010 at 3:39 PM

    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 audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Can User Technical Profile Influence AI Architecture Decisions?

By
In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...
Post a Comment
Read more

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

By
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.51 EF 6.0.2 VS2013 It see...
8 comments
Read more