What's cooking in git.git (topics)

Previous thread: [git-p4] log problem by injoin on Tuesday, June 17, 2008 - 11:07 pm. (1 message)

Next thread: What's in git.git (stable) by Junio C Hamano on Wednesday, June 18, 2008 - 12:32 am. (6 messages)
From: Junio C Hamano
Date: Wednesday, June 18, 2008 - 12:31 am

[Empty message]
From: Johan Herland
Date: Thursday, June 19, 2008 - 1:58 am

The first 3 patches (i.e. the bottom 3 in the above list) might be 
considered general cleanup patches, and are independent of each other (i.e. 
you might want to include them on their own merit, independently of patch 
#4).

The final patch doesn't make any difference for "regular" repos (e.g. 
git.git with ~200 refs) on Linux (see below). But once the number of refs 
increase, the difference becomes obvious.

Here are some numbers to give some more context:

All tests done on 64-bit quad-core Linux, cloning locally (hard-linked):

~200 refs (git.git):
current next:    0.2s
w/above patches: 0.2s

~1000 refs (test repo):
current next:    0.16s
w/above patches: 0.05s

~11000 refs (test repo):
current next:    1.3s
w/above patches: 0.3s

~26000 refs (actual repo at $dayjob):
current next:    3.2s
w/above patches: 0.8s


Regards,

...Johan

-- 
Johan Herland, <johan@herland.net>
www.herland.net
--

Previous thread: [git-p4] log problem by injoin on Tuesday, June 17, 2008 - 11:07 pm. (1 message)

Next thread: What's in git.git (stable) by Junio C Hamano on Wednesday, June 18, 2008 - 12:32 am. (6 messages)