From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Julian Phillips <julian@quantumfyre.co.uk>,
Jakub Narebski <jnareb@gmail.com>, Jan Holesovsky <kendy@suse.cz>
Subject: Re: Git benchmarks at OpenOffice.org wiki
Date: Wed, 2 May 2007 11:58:03 +0100 [thread overview]
Message-ID: <200705021158.04481.andyparkins@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705021046230.2425@reaper.quantumfyre.co.uk>
On Wednesday 2007 May 02, Julian Phillips wrote:
> A fully packed clone of the OOo git repo was indeed 1.3G, and the entrire
> checkout + repo was indeed 8.5G (using git 1.5.1.2).
I'm more confused now then. I assumed the figures were accurate, but they
cannot be:
CVS git SVN
Size of data on the server 8.5G 1.3G n/a
Size of checkout 1.4G 2.8G 1.5G
I don't doubt the 1.3G on the server - and assume that is fully packed. The
checkout sizes are suspicious though. Is that 2.8G packed?
- If it is, then we can deduce that this is a repo+source size, since the
server is packed size+0 therefore the size of the source tree is
2.8G - 1.3G = 1.5G
In which case the other figures are wrong:
- CVS checkout is 1.4G - impossible, the source tree is 1.5G. And where is
the overhead of the CVS directories which would make it more than 1.5G?
- SVN checkout overhead is always _at least_ the size of the source tree
because it keeps a pristine copy of HEAD. If the source tree is 1.5G,
then this figure should be at least 3G.
- If it is not, then we're back to "I don't believe that git was packed"
Something smells fishy here - either the source tree size is included in some,
but not in others or the git repository wasn't packed.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-05-02 10:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 21:46 Git benchmarks at OpenOffice.org wiki Jakub Narebski
2007-05-01 22:27 ` Junio C Hamano
2007-05-02 8:55 ` Andy Parkins
2007-05-02 9:51 ` Julian Phillips
2007-05-02 10:58 ` Andy Parkins [this message]
2007-05-02 14:28 ` Julian Phillips
2007-05-02 15:30 ` Andy Parkins
2007-05-02 17:11 ` Julian Phillips
2007-05-02 14:37 ` Jan Holesovsky
2007-05-02 15:33 ` Andy Parkins
2007-05-02 17:26 ` Junio C Hamano
2007-05-02 10:24 ` Johannes Schindelin
2007-05-02 11:33 ` Jakub Narebski
2007-05-02 14:55 ` Johannes Schindelin
2007-05-05 3:56 ` Linus Torvalds
2007-05-07 8:05 ` Junio C Hamano
2007-05-07 15:22 ` Linus Torvalds
2007-05-02 14:41 ` Jan Holesovsky
2007-05-02 16:24 ` Johannes Schindelin
2007-05-02 14:24 ` Jan Holesovsky
2007-05-02 14:35 ` Johannes Schindelin
2007-05-02 16:15 ` Petr Baudis
2007-05-02 16:27 ` Jan Holesovsky
2007-05-02 16:37 ` Petr Baudis
2007-05-02 16:48 ` Petr Baudis
2007-05-02 23:30 ` Jakub Narebski
2007-05-03 11:51 ` [tools-dev] " Jan Holesovsky
2007-05-03 12:54 ` Alex Riesen
2007-05-03 15:14 ` Johannes Sixt
2007-05-04 0:48 ` Jakub Narebski
2007-05-03 7:03 ` Florian Weimer
2007-05-03 9:33 ` Johannes Schindelin
2007-05-03 10:16 ` Robin Rosenberg
2007-05-03 10:48 ` Martin Langhoff
2007-05-06 20:05 ` Robin Rosenberg
2007-05-03 23:36 ` Jakub Narebski
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=200705021158.04481.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=julian@quantumfyre.co.uk \
--cc=kendy@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.