What does “Auto packing the repository for optimum performance” mean?

by

Short version: it means what it says, and if you just let it finish, all will be well.

During most operations which can potentially increase the number of loose (unpacked) objects in the repository (including pushes), Git invokes git gc --auto. If there are enough loose objects (by default, at least 6700), it will then invoke git repack -d -l to pack them. If there are too many separate packs, it will also repack them into one.

A pack is a delta-compressed single file, containing a large number of objects. It’s more efficient to store objects in packs, but it takes time to pack (compress) objects, so Git initially creates loose objects, then packs them in batches now and then, via automatic invocation of git gc --auto.

If you let Git finish repacking, this won’t happen again for a while. It can indeed take a while, especially if you have a lot of large binary objects, but if it’s triggering, then it’s a sign that it will probably drastically reduce the amount of disk space taken by the repo. If you really don’t want it to happen, you can change the config parameter gc.auto. If you increase it to something much larger than 6700, it will happen less frequently, but take longer when it does. If you decrease it, it’ll still have to do your current repack, but subsequently it will happen more often and finish more quickly. If you set it to 0, it will disable automatic repacking.

See man git-gc (under --auto) and man git-config (under gc.auto) for more information.

More Related Contents:

  1. How do I push a new local branch to a remote Git repository and track it too?
  2. Undoing a git rebase
  3. Force “git push” to overwrite remote files
  4. Undoing a ‘git push’
  5. What’s the difference between ‘git merge’ and ‘git rebase’?
  6. Combine the first two commits of a Git repository?
  7. Remove folder and its contents from git/GitHub’s history
  8. How to push to a non-bare Git repository?
  9. Can’t push to GitHub because of large file which I already deleted
  10. Git Push error: refusing to update checked out branch
  11. Warning: push.default is unset; its implicit value is changing in Git 2.0
  12. Rebasing a branch including all its children
  13. How do I recover/resynchronise after someone pushes a rebase or a reset to a published branch?
  14. How to inject a commit between some two arbitrary commits in the past?
  15. How do I delete a commit from a branch?
  16. Cannot push to Heroku because key fingerprint
  17. Remote origin already exists on ‘git push’ to a new repository
  18. Git push only for bare repositories?
  19. How to push a local Git repository to another computer?
  20. How to identify conflicting commits by hash during git rebase?
  21. Push to GitHub error: Couldn’t find host github.com in the .netrc file; using defaults
  22. Change old commit message using `git rebase`
  23. What is the difference between git pull and git fetch + git rebase?
  24. Rebase feature branch onto another feature branch
  25. Making a Git push from a detached head
  26. Pushing from local repository to GitHub hosted remote
  27. Your branch is ahead of ‘origin/master’ by 3 commits
  28. git push heroku master says “Everything up-to-date”, but the app is not current
  29. How to retain commit gpg-signature after interactive rebase squashing?
  30. Can tags be automatically moved after a git filter-branch and rebase?

Leave a Comment