Am 04.05.2010 22:42, schrieb Allison Randal:
On 5/4/10 9:26 PM, Patrick R. Michaud wrote:
On Tue, May 04, 2010 at 09:03:23PM +0100, Allison Randal wrote:
What I don't understand is what advantage we gain from
using git as the central data-store.
Speed. Performing git clones of svn repositories is extremely painful
and wasteful of resources.
Ah, that makes sense. When people talked about "speed" in the IRC
discussion it really didn't make sense, as svn and git are about
equivalent in day-to-day usage terms. But the git-svn link being slow I
can see.
You must have a very fast internet connection. I haven't.
(yes, I do 'log' without limits to search in commit messages)
$ time svn log > /dev/null
real 1m44.351s
$ time git log > /dev/null
real 0m2.265s
on second execution:
$ time git log > /dev/null
real 0m0.900s
Show last commit (I use that quite a lot):
$ time svn diff -r 46297:46298 > /dev/null
real 0m10.865s
$ time git show > /dev/null
real 0m0.063s
Show all changes in working copy (I use that even more often):
$ time svn diff > /dev/null
real 0m0.542s
$ time git diff >/dev/null
real 0m0.030s
Current status (also used a lot):
$ time svn status > /dev/null
real 0m0.703s
$ time git status >/dev/null
real 0m0.230s
(Note: this was done on a git-svn mirror of parrot trunk, and an svn
checkout of the 'codestring' branch since I had that ready)
(Second note: I would have liked to compare commit and update/pull
speed, but it's rather hard to do in a meaningful way, since they do
different things in svn and git. That said I do think I observe that git
is way faster with updating a rather outdated repository; fetching a few
hundred or even thousand revisions with svn is often painfully slow).
Not all of these speed differences actually matter in real-world
development, but many of them do. Once you get used to git's speed, you
don't want to miss it again.
Cheers,
Moritz
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
