@@ -28,7 +28,7 @@ This edition covers what happened during the months of January and February 2026
2828
2929### Support
3030
31- * [ Slow git pack-refs --all] ( https://www.google.com/search?q=https:// lore.kernel.org/git/CH3PR12MB9026B5872FD42F031970074BC2B3A%40CH3PR12MB9026.namprd12.prod.outlook.com )
31+ * [ Slow git pack-refs --all] ( https://lore.kernel.org/git/CH3PR12MB9026B5872FD42F031970074BC2B3A%40CH3PR12MB9026.namprd12.prod.outlook.com )
3232
3333 Martin Fick started the discussion by reporting a significant
3434 performance issue where ` git pack-refs --all ` was taking over five
@@ -50,7 +50,7 @@ This edition covers what happened during the months of January and February 2026
5050 brian m. carlson replied to Martin, suggesting that the slowdown
5151 might be occurring in ` should_pack_ref() ` because Git needs to
5252 verify that the object at the end of a reference actually
53- exists. Brian also pointed out that NFS was likely a major factor,
53+ exists. brian also pointed out that NFS was likely a major factor,
5454 as the network latency involved in opening many pack files and
5555 checking loose objects can be substantial. He suggested setting
5656 ` receive.unpackLimit ` to 1 to reduce the number of loose objects
@@ -98,11 +98,16 @@ This edition covers what happened during the months of January and February 2026
9898 re-peel every reference by looking up the objects in the pack files
9999 over the slow NFS connection.
100100
101- The discussion concluded with the identification of a specific
102- interoperability issue between JGit and Git. By identifying that the
103- missing ` fully-peeled ` header was causing redundant, expensive I/O
104- operations, Martin was able to plan a fix for JGit that would
105- resolve the performance bottleneck on his production servers.
101+ Following that discovery, a fix was proposed for JGit in
102+ [ Change 1230152] ( https://eclipse.gerrithub.io/c/eclipse-jgit/jgit/+/1230152 ) .
103+ Adithya Chakilam submitted the patch, titled "pack-refs: Add
104+ sorted/fully-peeled flags," to ensure JGit produces packed-refs
105+ files that Git can process efficiently.
106+
107+ This resolution not only fixes the immediate performance issue for
108+ Gerrit servers but also ensures that any environment using a mix of
109+ JGit and Git will benefit from reduced lock contention and faster
110+ reference updates.
106111
107112<!-- -
108113## Developer Spotlight:
0 commit comments