Re: expensive local git clone

[David S. Miller]

From: Petr Baudis [EMAIL PROTECTED]
Date: Mon, 4 Jul 2005 22:42:35 +0200

 Dear diary, on Mon, Jul 04, 2005 at 10:39:09PM CEST, I got a letter
 where Linus Torvalds [EMAIL PROTECTED] told me that...
  That said, the pack-file thing I'm working on won't be perfect either, and
  the main advantage is that it should work over ssh. The fastest way to do
  a clone is really to do a recursive hardlinked tree, so you may well want
  to just do
  
  #!/bin/sh
  mkdir $2  cp -rl $1/.git $2/.git
  
  and it should be about a million times faster and equally effective.
  
  Untested, of course.
 
 I wouldn't do that on anything but .git/objects. ;-)

Agreed.  When I do it by hand (but I shouldn't have to
do this by hand, git-clone-script should do it this way
if that's the best and most efficient) I usually link the
object directory then copy the rest of the stuff non-linked.

I keep hoping git-clone-script is going to be a good way
to clone two local trees.  Is my hope misguided?  :-)
-
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] write-tree performance problems

[David S. Miller]

On Wed, 20 Apr 2005 10:06:15 -0700 (PDT)
Linus Torvalds [EMAIL PROTECTED] wrote:

 I bet your SHA1 implementation is done with hand-optimized and scheduled
 x86 MMX code or something, while my poor G5 is probably using some slow
 generic routine. As a result, it only improved by 33% for me since the
 compression was just part of the picture, but with your cheap SHA1 the
 compression costs really dominated, and so it's almost four times faster
 for you.

The openssl tree has a i586 optimized SHA1 implementation.
A quick scan of the 0.9.7e tree I happen to have lying around
shows there aren't optimized for other cpus in there, just i586.
-
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html