Jeff King <peff@xxxxxxxx> writes: >> ... git repack ... --max-pack-size=<desired pack size> to create split and >> smaller packs instead. > ... > You can also set pack.packSizeLimit for the latter, though I do not > recommend it. It will not help with memory usage (neither while > repacking nor for later commands). In other words, passing --max-pack-size, whether it is done with a new --repack-arguments option or it is done with the existing pack.packSizeLimit configuration, would make things worse. So in conclusion: - attempting to repack everything into one pack on a memory starved box would be helped with reduced window memory size. - on a small box, it may make sense to avoid repacking everything into one in the first place, but we do not want the number of packs to grow unbounded. Would the new geometric repack feature help here, especially for the latter?
