Skip to main content

Speed up your Git experience by enabling the commit graph algorithm

While working in Visual Studio today I noticed a message appear at the top my idea. The message stated the following:

Speed up your git experience in Visual Studio by enabling the git commit graph algorithm.

No idea what that exactly means but that sounds promising… so let’s find out

Why this commit graph algorithm?

Git repositories can become sluggish as they grow in size and complexity. If you've ever waited impatiently for git log to load or noticed that branch operations take longer than they should, you're not alone. Recently, Git introduced a powerful feature that can dramatically improve performance: the commit graph algorithm.

The commit graph is a data structure that Git uses to store precomputed information about your repository's commit history. Instead of traversing the entire commit tree every time you run commands like git log, git merge-base, or git show-branch, Git can use this precomputed graph to answer queries much faster.

Think of it as an index for your commit history—similar to how a database index speeds up queries by avoiding full table scans.

The commit graph algorithm precomputes and stores several key pieces of information:

  1. Generation numbers: How far each commit is from the root commits
  2. Commit dates: Timestamp information for faster chronological queries
  3. Tree and parent hashes: Direct access to commit metadata
  4. Reachability bloom filters: Probabilistic data structures for quick ancestor checks

This precomputed data allows Git to:

  • Skip unnecessary commit traversals
  • Use mathematical shortcuts for common queries
  • Provide O(1) or O(log n) performance for operations that previously required O(n) time

Enabling the Commit Graph

Visual Studio will try to predict when enabling the commit graph could enhance performance. In that case the notification I mentioned in the intro is shown and you only need to click on enable.

You can also manually enable the commit-graph by going to Git > Settings > Enable commit graph for better Git performance.

Remark: When the commit graph is enabled, it can take several seconds up to a couple of minutes depending on the size of your repository before the commit graph is generated. So be patient!

As this is a git feature not specifically linked to Visual Studio, you can also activate this directly at the git level:

  • First, configure Git to automatically maintain the commit graph:

git config core.commitGraph true

  • This tells Git to use the commit graph for read operations when available.
  • To keep the commit graph up-to-date automatically:

git config gc.writeCommitGraph true

  • This ensures the commit graph gets updated during garbage collection operations.
  • As a last step for existing repositories, you'll need to generate the commit graph manually:

git commit-graph write --reachable

Remark: Starting from Git version 2.24.0, core.commitGraph and gc.writeCommitGraph are on by default, so you don’t need to set the config manually.

More information

Supercharge your Git experience in VS - Visual Studio Blog

Updates to the Git Commit Graph Feature - Azure DevOps Blog

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more