Packfiles and compression in Git - Commands & Configuration

Introduction

Git stores many versions of files efficiently by grouping objects into packfiles and compressing them. This saves space and speeds up data transfer when sharing repositories.

When your Git repository has many objects and you want to reduce disk space usage.

When you want to speed up cloning or fetching by sending compressed data.

When you want to optimize your repository after many commits and branches.

When you want to inspect or troubleshoot how Git stores data internally.

When you want to manually repack objects to improve performance.

Commands

This command cleans up unnecessary files and optimizes the local repository by creating packfiles and compressing objects.

Terminal

git gc

Expected Output

Enumerating objects: 1000, done.

Counting objects: 100% (1000/1000), done.

Delta compression using up to 8 threads

Compressing objects: 100% (800/800), done.

Writing objects: 100% (1000/1000), done.

Total 1000 (delta 600), reused 0 (delta 0)

→

--aggressive - Makes the compression more thorough but slower.

Shows statistics about loose and packed objects, including disk space used and packfile count, to verify compression status.

Terminal

git count-objects -vH

Expected Output

count: 0

size: 0 bytes

in-pack: 1000

packs: 1

size-pack: 1.2 MiB

prune-packable: 0

garbage: 0

size-garbage: 0 bytes

→

-v - Shows verbose output with detailed stats.

→

-H - Shows sizes in human-readable format.

Inspects the contents of packfiles, showing object hashes, types, sizes, and compression details.

Terminal

git verify-pack -v .git/objects/pack/pack-*.idx | head -5

Expected Output

e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 blob   0 0 0

4b825dc642cb6eb9a060e54bf8d69288fbee4904 tree   0 0 0

f5b7d3a6a1f3e8a3b7c9a4e8b1a2c3d4e5f6a7b8 commit 234 123 45

...

Key Concept

If you remember nothing else from this pattern, remember: Git uses packfiles to group and compress many objects efficiently, saving space and speeding up operations.

Common Mistakes

Running git gc too frequently or on very large repositories without --aggressive.

It can cause unnecessary CPU load and slow down your system.

Run git gc only when needed or use --aggressive for deep compression during maintenance.

Deleting packfiles manually from the .git/objects/pack directory.

This corrupts the repository and causes data loss.

Use git commands like git gc or git repack to manage packfiles safely.

Ignoring packfile inspection and troubleshooting when repository size grows unexpectedly.

You miss opportunities to optimize and fix repository issues.

Use git verify-pack and git count-objects to understand and manage packfiles.

Summary

git gc creates packfiles and compresses objects to optimize repository storage.

git count-objects -vH shows detailed stats about packed and loose objects.

git verify-pack inspects packfile contents for troubleshooting and analysis.