From: Jan Hudec <bulb@ucw•cz>
To: "Björn Steinbrink" <B.Steinbrink@gmx•de>
Cc: Sean Brown <seanmichaelbrown@gmail•com>, git@vger•kernel.org
Subject: Re: git repository size vs. subversion repository size
Date: Sun, 13 Apr 2008 11:57:08 +0200 [thread overview]
Message-ID: <20080413095708.GA16649@efreet.light.src> (raw)
In-Reply-To: <20080405023437.GA8861@atjola.homenet>
On Sat, Apr 05, 2008 at 04:34:37 +0200, Björn Steinbrink wrote:
> On 2008.04.04 22:27:12 -0400, Sean Brown wrote:
> > On Fri, Apr 4, 2008 at 6:17 PM, Björn Steinbrink <B.Steinbrink@gmx•de> wrote:
> > > On 2008.04.04 18:02:56 -0400, Sean Brown wrote:
> > > > Last night I decided to see what storage size differences I might see
> > > > between an svn repo and a git one. So I imported a highly used
> > > > subversion repository into git and was shocked to see how huge the git
> > > > version was. I used a repo that has a lot of branches and tagged
> > > > releases just to make sure importing into git would in fact keep all
> > > > of the history. It did keep the history, but the total disk usage was
> > > > very different:
> > > >
> > > > $subversionbox # du -hs ./my_sample_website/
> > > > 67M ./my_sample_website
> > > >
> > > > $localhost # du -hs ./git-samplesite/
> > > > 3.6GB ./git-samplesite/
> > >
> > > How much of that is in the .git/svn directory? The contents of that
> > > directory are used to map git commits to svn revision and git versions
> > > before 1.5.4 had a quite space consuming file format for that. The new
> > > format is a lot better. If you want to switch completely, you can even
> > > just delete the .git/svn directory, as that's only required as long as
> > > you want to interact with the corresponding svn repository.
> > >
> > > And finally, you might want to repack to repository once after the
> > > initial import, to get a smaller repo. Something like:
> > > git repack -a -d -f --window=100 --depth=100
> > >
> >
> > The svn folder (in the.git directory) was only about 4.2 MB. After
> > running the repack (and then after that git gc as mentioned by another
> > in this thread), it's still about 3.5 GB.
> >
> > git-samplesite (master)]$ du -hs ./*
> > 2.1G ./branches
> > 1.4G ./tags
> > 66M ./trunk
>
> Uhm, you forgot to use -s when doing the clone. That would have created
No, not the clone, but the git svn init.
> real git branches instead of the directories... What you are counting is
> the size of the checked out, uncompressed files of _all_ branches and
> _all_ tags (and trunk). The repo size of basically what "du -sh .git"
> would give.
>
> Björn
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger•kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jan 'Bulb' Hudec <bulb@ucw•cz>
next prev parent reply other threads:[~2008-04-13 9:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 22:02 git repository size vs. subversion repository size Sean Brown
2008-04-04 22:17 ` Björn Steinbrink
2008-04-04 23:49 ` Stephen Bannasch
2008-04-05 0:01 ` Steven Walter
2008-04-05 0:04 ` Stephen Bannasch
2008-04-05 0:18 ` Björn Steinbrink
2008-04-14 15:28 ` Eric Hanchrow
2008-04-05 2:27 ` Sean Brown
2008-04-05 2:34 ` Björn Steinbrink
2008-04-13 9:57 ` Jan Hudec [this message]
2008-04-05 3:11 ` Shawn O. Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080413095708.GA16649@efreet.light.src \
--to=bulb@ucw$(echo .)cz \
--cc=B.Steinbrink@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=seanmichaelbrown@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox