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

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

By
The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...
Post a Comment
Read more

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

By
Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...
Post a Comment
Read more