Doc Request: The importance of `Total size` about git-sizer

[mhagger]

When the uncompressed size is much larger than the on-disk size, that is an indication that things are compressing very well. That's usually because there are large blobs or large trees that are getting modified incrementally many times.

The overall uncompressed size of all objects is a good indication of how expensive commands like git gc --aggressive (and git repack [-f|-F] and git pack-objects --no-reuse-delta), git fsck, and git log [-G|-S] will be.

The uncompressed size of trees and commits is a good indication of how expensive reachability traversals will be, including clones and fetches and git gc. (Bitmaps can help here for some commands.)

[alejandro5042]

Thanks for the reply! Makes sense. To close this issue, should we document any of this in the README?