Lock contention during automatic garbage collection in shared repositories

Question

The goal is to determine whether Git's automatic garbage collector can safely run alongside concurrent fetch or push operations in a shared repository without introducing latency spikes or lock failures.
Git describes gc.auto as a threshold-based trigger, but it does not guarantee serialization of repository writes. When multiple Git processes access the same object database, automatic packfile repacking may start while another process reads or writes packs. Locking behavior varies by operating system and Git version, so it is unclear whether the collector defers to existing locks or proceeds and causes contention.

Does Git serialize automatic garbage collection with concurrent fetch or push operations?
Can gc.auto be disabled per repository to eliminate conditional latency under load?
Which lock files indicate contention between git gc and simultaneous repository access?

Wasi · Answer

Git Automatic Garbage Collection and Concurrent Operations
Git does not automatically serialize its garbage collection (gc) with concurrent fetch or push operations. Both processes can run in parallel, leading to potential lock contention on pack files, which manifests as temporary latency spikes or failures, not guaranteed serialization.
Confirmed Behavior and Mitigation

Automatic GC triggers based on object count thresholds, not exclusive access guarantees.
Concurrent operations (fetch/push) will typically wait for active pack file locks to clear.
To eliminate conditional latency spikes, setting gc.auto to 0 disables automatic triggering, requiring manual execution during off-peak times.

Diagnostic Indicators
Contention is indicated by the presence of lock files such as .git/objects/pack/pack-*.pack.lock or pack-*.idx.lock during an operation. Stale locks from crashed processes can block subsequent access.
The necessary step to test the impact of automatic triggering is to set gc.auto to 0 per repository and then repeat the concurrent fetch/push test.

Lock contention during automatic garbage collection in shared repositories

1 answer

Git Automatic Garbage Collection and Concurrent Operations

Confirmed Behavior and Mitigation

Diagnostic Indicators

Your perspective belongs here.

0 question comments