Is the git storage model wasteful?
I was reading about how git stores changes here.
It sounds like if I change one line in a file, it’s going to re-store the entire file. Does this waste a lot of space compared to say, Subversion which only stores diffs?
- Git for Local Branches
- Mercurial diff not working after move/rename
- Using git flow, how would I revert back to a previous release?
- Append gerrit patch-set if commits were done locally
- Reverting entire git repository to a specific version
- What is the meaning of git reset --hard origin/master?
(Or am I misunderstanding the storage model?)
3 Solutions collect form web for “Is the git storage model wasteful?”
Git will eventually pack everything into delta-compressed archives during the regular course of its internal maintenance, at which point this is no longer an issue.
This isn’t really an issue today though. Git’s philosophy is that disk space is cheap, and it’s better optimize for speed rather than storage efficiency. Chances are you’ll be better served by a SCM which is twice as fast, as opposed to one which requires half the disk space.
See the Git Book’s chapter on The Packfile as well as git repack and git-pack-objects.
Git does compress stored files with with zlib and it also packs them for a more efficient storage.
Actually not. There is a good article describing the advantage of git: http://web.archive.org/web/20110902055701/http://whygitisbetterthanx.com:80/