On Wednesday 20 April 2005 11:40, Linus Torvalds wrote:

On Wed, 20 Apr 2005, Chris Mason wrote:

quoted

Thanks for looking at this.  Your new tree is faster, it gets the commit
100 patches time down from 1m5s to 50s.

It really _shouldn't_ be faster. It still does the compression, and throws
the end result away.

Well, that's a little odd.  I had thought about making sure you did this 
change and forgotten.  1 minute benchmarks are a horrible idea since they run 
into noise with cache writebacks.  I should know better...

At any rate, the time for a single write-tree is pretty consistent.  Before it 
was around .5 seconds, and with this change it goes down to .128s.  My patch 
was .024.

The 100 patch time is down to 32s (3 run average).  This is close enough that 
I don't think my patch is worth it if no other part of git can benefit from 
having trees in the index.

To actually go faster, it _should_ need this patch. Untested. See if it
works..

Thanks. This one missed the filling in the returnsha1.  New patch attached.

-chris