On 8/24/07, Jon Smirl <jonsmirl@xxxxxxxxx> wrote: > We're going something wrong in git-daemon. I can clone the tree in > five minutes using the http protocol. Using the git protocol would > take 24hrs if I let it finish. 20Mb/s to kernel.org time git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git real 2m34.629s 20Mb/s to kernel.org time git clone http://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git real 3m52.203s Same kernel from my NSLU2 over http (100Mb/s) time git clone http://jonsmirl.is-a-geek.net/apache2-default/mpc.git real 2m36.227s Using git protocol to nslu2 takes 24hrs On 8/24/07, Nicolas Pitre <nico@xxxxxxx> wrote: > Try running "git repack -a" directly on the NSLU2. You should have the > same performance problems as with a clone. This is true, it would take over 24hrs to finish. Is their a reason why initial clone hasn't been special cased? Why can't initial clone just blast over the pack file already sitting on the disk? I also wonder if a little application of some sorting to in-memory data structures could help with the random IO patterns. I'm getting the same data out of a stupid HTTP server and it doesn't go all IO bound on me so a solution has to be possible. -- Jon Smirl jonsmirl@xxxxxxxxx - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
