Git 2.38 Introduces Scalar: Boosting Performance for Massive Repositories
Git 2.38 adds Microsoft’s Scalar tool to the core, offering pre‑configured optimizations like file‑system monitoring, multi‑pack indexing, commit graphs, background maintenance, partial clone and sparse checkout, plus a new git rebase --update-refs option for faster handling of huge repositories.
Git 2.38 has been released, with the most notable change being the integration of Microsoft’s repository management tool Scalar, designed to handle massive Git repositories.
Introduce the massive Git repository management tool Scalar
Scalar is a .NET Core application originally written in C# and later rewritten in C. It optimizes Git command performance by applying recommended configuration values and running background maintenance, accelerating Git operations regardless of the hosting service. Microsoft states that registering the largest repositories with Scalar yields immediate speed improvements.
Git has continuously improved handling of large repositories, and Scalar adds a pre‑configured set of features such as an internal file‑system watcher, multi‑pack index, commit graph, background maintenance, partial clone, and sparse checkout.
Scalar, initially a Microsoft‑led open‑source project intended for contribution to Git, is now part of the mainline Git 2.38 codebase.
Git 2.38 also adds a new git rebase option --update-refs, which updates dependent branches during a rebase.
For more details, see the official release announcement: https://github.blog/2022-10-03-highlights-from-git-2-38/
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Programmer DD
A tinkering programmer and author of "Spring Cloud Microservices in Action"
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
