Git contributors detail performance fixes for deleting references
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.
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.
- Git's files backend stores each reference as a separate loose file, which doesn't scale well for repositories with millions of refs.
- The reftable backend, introduced in Git 2.45, is designed to address these scalability issues and will become Git's default in version 3.0.
- Large monorepos, like GitLab's with over 15 million references, illustrate real-world cases where reference storage performance matters.
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.