Leverage pack.useSparse
pack.useSparse When true, git will default to using the --sparse option in git pack-objects when the --revs option is present. This algorithm only walks trees that appear in paths that introduce new objects. This can have significant performance benefits when computing a pack to send a small change. However, it is possible that extra objects are added to the pack-file if the included commits contain certain types of direct renames. Default is false unless feature.experimental is enabled.
This would help for .com and our customers, got recommended in: omnibus-gitlab!4050 (merged). part of closing this issue is removing the custom config value on omnibus.
For the implementation, please first investigate why this feature is still experimental. If we do require a feature flag, and if we should actually ship this in the current release.