Heya, I just read this blog post [0] in which one of the Pidgin devs sheds his light on their 'tool choice'. In the post he mentions the following figures: "I don't mind the database, myself. I have 11 working copies (checkouts) from my single pidgin database (8 distinct branches, plus duplicates of the last three branches I worked on or tested with). Each clean checkout (that is, a checkout prior to running autogen.sh and building) is approximately 61 MB. If this were SVN, each working copy would be approximately 122 MB due to svn keeping a pristine copy of every file to facilitate 'svn diff' and 'svn revert' without needing to contact the server the working copy was pulled from. Now, let's add that up. For SVN, I would have 11 times 122 MB, or 1342 MB, just in working copies. For monotone, I have 11 times 61 MB for the working copies (671 MB), plus 229 MB for the database, for a grand total of 900 MB. For me, this is an excellent bargain, as I save 442 MB of disk space thanks to the monotone model. For another compelling comparison that's sure to ruffle a few feathers, let's compare to git. If I clone the git mirror of our monotone repository, I find a checkout size of 148 MB after git-repack--running git-gc also increased the size by 2 MB, but I'll stick with the initial checkout size for fairness. If I multiply this by my 11 checkouts, I will have 1628 MB. This is even more compelling for me, as I now save 728 MB of disk space with monotone." I'm in the process of cloning the repo myself, and will check if doing a more aggressive (high --window and --depth values) repack will get us below that 148, but I'm thinking it's just that big a repo. Anyway, it seems git is getting screwed over in this post because he is not taking advantage of git's object-database-sharing capabilities. Am i right in thinking that with git-new-workdir we would end up at 61*11+148 = 819MB? (Which would actually put us below monotone by 80MB.) Not that I care much whether monotone or git is smaller in disk size, I'm just curious if we indeed offer this capability? Perhaps someone with more knowledge of git-new-workdir could shed a light? [0] http://theflamingbanker.blogspot.com/2008/07/holy-war-of-tool-choice.html -- Cheers, Sverre Rabbelier -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
