Over a million developers have joined DZone.

Why You Should Optimize Your Local Git Repository From Time to Time

DZone's Guide to

Why You Should Optimize Your Local Git Repository From Time to Time

With SSD for Git, you can use GIt without any performance problems — even when you've got some large repositories. Read on to find out how.

Free Resource

Learn how real real-time monitoring is critical for DevOps. Because you can't build what you can't see.

Git is an exceptional piece of software and I really cannot think about living without it. And now, with super fast SSD, you can use Git without performance problems — even for large repositories (for example, maybe you converted an old Subversion or TFVC).

When your repository has thousands of objects, and especially if you adopt flows of work where you rebase often, your repository probably has a large number of unnecessary objects that can be deleted safely. Git runs for you in the background a special command called:

git gc

It is a garbage collection command that will clean up your local repository. Nothing changes in the remote repository. Sometimes, you can also manually run a deeper cleaning of your repository with this command:

git gc --aggressive

You can run this from time to time (documentation says you can run every few hundred commits). It will take longer that a normal git gc, but it will help in keeping your local Git repository fast — even if you work with a really large codebase.

Get real-time alerts and visualizations across your cloud infrastructure for real real-time cloud monitoring. Try it FREE now

performance ,git ,optimization ,git repositories

Published at DZone with permission of Ricci Gian Maria, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}