Skip to content
Tech News
← Back to articles

Git contributors detail performance fixes for deleting references

read original more articles
GoKawiil Brief

A technical write-up examines how Git's default 'files' reference backend stores branches and tags as individual loose files, and how this design creates slowdowns and filesystem overhead when references are deleted at scale. It contrasts this with the newer reftable backend introduced in Git 2.45, which is intended to replace the files backend as Git's default starting with version 3.0.

Why It Matters

GoKawiil's interpretation of the reporting above, not reported fact.

Repositories with millions of references, such as GitLab's main monorepo with over 15 million refs, can suffer from slow iteration, inode bloat, and lack of atomic updates under the older files backend, according to the write-up. Optimizing deletions and adopting reftable could meaningfully improve performance for large-scale Git hosting providers and enterprises managing huge codebases.

Key Takeaways

Source: nayak.im, 2026-11-08

Published there as: “Optimizing Reference Deletions in Git”

Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.
Keep reading
git 51 briefs → gitlab 22 briefs →