On Mon, Nov 27, 2017 at 03:28:37PM -0500, Richard Hipp wrote: > I didn't try any repacking. I merely ran "git clone" then looked at > the packfile in .git/objects/pack. You would think that the server > would want to do an aggressive repack before sending the packfile > across a clone, to save bandwidth. But maybe GitHub values CPU cycles > more than bandwidth...
git import is writing pretty dumb packs. Lots of redundancy in it, so it's not really that surprising. It's kind of similar to the effect of avoiding "fossil rebuild --compress" or Mercurial's generic delta. Cloning IIRC will mostly use the deltas as recorded, it doesn't recompute them. GitHub in generally naturally avoids CPU load as much as possible, since it is one of the more expensive parts of running in the cloud. > Your git-foo is much greater than mine, Joerg. Can you please clone > https://github.com/mackyle/sqlite.git and see if you can get the > packfile to come out smaller? git repack -A -d --depth=500 --window-memory 4g -f -F gives me around 43MB for .git. Joerg _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
