From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org
Cc: dev@bitmover.com
Subject: boring BK stats
Date: Sun, 22 Sep 2002 16:56:04 -0700 [thread overview]
Message-ID: <200209222356.g8MNu4V10172@work.bitmover.com> (raw)
I should be working on getting the bk-3.0 release done but I'm sick of
fixing BK-on-windows bugs...
Linus' kernel tree has 13333 revision controlled files in it. Without
repository compression, it eats up 280M in an ext2 fs. With repository
compression, that drops to 129M. After checking out all the files, the
size of the revision history and the checked out files is 317MB when
the revision history is compressed. That means the tree without the
history is 188MB, we get the revision history in less space than the
checked out tree. That's pretty cool, by the way, I know of no other
SCM system which can say that.
Checking out the tree takes 16 seconds. Doing an integrity check takes 10
seconds if the repository is uncompressed, 15 seconds if it is compressed.
That's on 1.3Ghz Athlon w/ PC133 memory running at the slower CAS rate,
but lots of it, around 900MB.
An integrity check checksums the entire revision history and does a
checkout into /dev/null to make sure that both the overall and most
recent delta checksums are valid.
There are about 8600 changesets in the tree. There have been 76998
deltas made to the tree since Feb 05 2002. That's an average of 37
changesets and 333 deltas per *day* seven days a week. If you assume
a 5 day work week then the numbers are 52 csets/day and 466 deltas/day.
Those changerate numbers are pretty zippy. You guys are rockin'.
As for syncs with bkbits, I dunno, my guess is we're pushing 300,000 pulls
or so. We're nowhere near to saturating the T1 line so BK compression
stuff is working well.
next reply other threads:[~2002-09-22 23:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-22 23:56 Larry McVoy [this message]
2002-09-23 2:01 ` boring BK stats Jeff Garzik
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=200209222356.g8MNu4V10172@work.bitmover.com \
--to=lm@bitmover.com \
--cc=dev@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).