From: Craig Boston <craig@olyun.gank.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Efficient way to import snapshots?
Date: Mon, 30 Jul 2007 17:20:28 -0500 [thread overview]
Message-ID: <20070730222028.GE64467@nowhere> (raw)
In-Reply-To: <alpine.LFD.0.999.0707301240330.4161@woody.linux-foundation.org>
>
> [ snip lots of helpful comments from various people ]
>
I just wanted to say thanks to Linus and Junio and everyone who
commented, I think I have a much more workable solution now. With my
brute-force remove and re-add everything script the times for import
looked like this:
Importing /compile/co/RELENG_4 (no changes):
svk import: 166.86 seconds
git: 455.82 seconds
Importing /compile/co/RELENG_6:
svk import: 203.69 seconds
git: 796.48 seconds
Importing /compile/co/HEAD:
svk import: 243.90 seconds
git: 837.13 seconds
Ok, so I remembered wrong, git was only 4x slower. Still, I knew it
could do better than that...
After transplanting the .git directory from 3 cloned repositories
checked out to the appropriate branch into the CVS checkout directories,
priming them with a 'git status', and using the git ls-file | git
update-index trick followed by commit -a, here are the revised times:
# On branch cvs_RELENG_4
nothing to commit (working directory clean)
git: 67.65 seconds
Created commit 106bc0b: Import 20070730 snapshot
7 files changed, 259 insertions(+), 75 deletions(-)
Git repository at /compile/co/RELENG_6/src updated
git: 62.02 seconds
Created commit 776031b: Import 20070730 snapshot
86 files changed, 10929 insertions(+), 587 deletions(-)
[snip lots of lines for added files]
Git repository at /compile/co/HEAD/src updated
git: 61.77 seconds
_MUCH_ better. I knew it had to be capable of faster :-)
Again, thanks for all the help. I look forward to seeing what else git
can do!
Craig
next prev parent reply other threads:[~2007-07-30 22:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 18:07 Efficient way to import snapshots? Craig Boston
2007-07-30 18:56 ` Linus Torvalds
2007-07-30 19:29 ` Craig Boston
2007-07-30 19:52 ` Linus Torvalds
2007-07-30 20:10 ` Craig Boston
2007-07-30 21:29 ` Junio C Hamano
2007-07-30 21:49 ` Craig Boston
2007-07-30 21:04 ` Junio C Hamano
2007-07-30 23:19 ` Linus Torvalds
2007-07-30 21:55 ` Junio C Hamano
2007-07-30 23:27 ` Linus Torvalds
2007-07-30 23:59 ` Junio C Hamano
2007-07-31 0:45 ` Linus Torvalds
2007-07-31 0:47 ` Junio C Hamano
2007-07-30 22:20 ` Craig Boston [this message]
2007-07-30 23:30 ` Linus Torvalds
2007-07-31 1:17 ` Craig Boston
2007-07-31 1:44 ` Linus Torvalds
2007-07-31 4:23 ` Theodore Tso
2007-07-31 13:53 ` Craig Boston
2007-07-31 15:50 ` Linus Torvalds
2007-07-31 16:15 ` Theodore Tso
2007-07-31 6:23 ` David Kastrup
2007-07-31 7:54 ` Florian Weimer
2007-07-31 8:48 ` David Kastrup
2007-07-30 21:22 ` Jakub Narebski
2007-07-30 21:54 ` David Kastrup
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=20070730222028.GE64467@nowhere \
--to=craig@olyun.gank.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@linux-foundation.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).