On 31/10/2021 18:35, skybuck2000 wrote: > > Git stores snapshots. It will > > > I may have noticed this. I did notice the GIT database can get quite > large. One example is PascalCoin... it's git database seems to be 100 > MB... it shouldn't be that big I think, I don't think the sources are > that big, so this may be because of copies of all different versions > stored ? > > > _show_ diffs between commits, but it's still between snapshots. It is > only later at the database level that compression is applied. > > > Are all snapshots stored in the git database uncompressed ?
Not quite, see below > > What do you mean with database and compression, is it applied later > automatically by git ? Yes, the compression, called "packing" is done automatically when various size limits (usually heuristic) are reached. See https://github.com/git/git/blob/master/Documentation/technical/pack-heuristics.txt for how it's done ("magic" tada!) > > For example when I "download"/pull a git repository I do see some zip > extraction going on... and sometimes maybe also further pulls. > Is that only done for the communication/protocol part to cut bandwidth > costs ? Packing all the way down & up! > > Or is the git database later re-zipped ? For example after a GIT commit ? > > Come to think of it, compression might eat into time... so maybe GIT > doesn't do much compression when day to day work and committing ? It's quite fast because it knows how to cheat - see above. Often folks will have overnight packing (server management style) so as to keep any delays out of the way. Philip -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/cde7ab14-ad68-340f-57b3-becb5a3d8c09%40iee.email.
