Revision f43ba60e2c3bec4925eee229fa0f420dd1296f0c authored by Linus Torvalds on 13 April 2006, 17:01:02 UTC, committed by Junio C Hamano on 13 April 2006, 18:26:56 UTC
This trivially avoids keeping the commit message data around after we
don't need it any more, avoiding a continually growing "git log" memory
footprint.

It's not a huge deal, but it's somewhat noticeable. For the current kernel
tree, doing a full "git log" I got

 - before: /usr/bin/time git log > /dev/null
	0.81user 0.02system 0:00.84elapsed 100%CPU (0avgtext+0avgdata 0maxresident)k
	0inputs+0outputs (0major+8851minor)pagefaults 0swaps

 - after: /usr/bin/time git log > /dev/null
	0.79user 0.03system 0:00.83elapsed 100%CPU (0avgtext+0avgdata 0maxresident)k
	0inputs+0outputs (0major+5039minor)pagefaults 0swaps

ie the touched pages dropped from 8851 to 5039. For the historic kernel
archive, the numbers are 18357->11037 minor page faults.

We could/should in theory free the commits themselves, but that's really a
lot harder, since during revision traversal we may hit the same commit
twice through different children having it as a parent, even after we've
shown it once (when that happens, we'll silently ignore it next time, but
we still need the "struct commit" to know).

And as the commit message data is clearly the biggest part of the commit,
this is the really easy 60% solution.

Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
1 parent d533524
History
File Mode Size
t-apply-1.expect -rw-r--r-- 544 bytes
t-apply-1.patch -rw-r--r-- 5.5 KB
t-apply-2.expect -rw-r--r-- 218 bytes
t-apply-2.patch -rw-r--r-- 1.9 KB
t-apply-3.expect -rw-r--r-- 317 bytes
t-apply-3.patch -rw-r--r-- 12.8 KB
t-apply-4.expect -rw-r--r-- 193 bytes
t-apply-4.patch -rw-r--r-- 245 bytes
t-apply-5.expect -rw-r--r-- 885 bytes
t-apply-5.patch -rw-r--r-- 12.7 KB
t-apply-6.expect -rw-r--r-- 232 bytes
t-apply-6.patch -rw-r--r-- 2.3 KB
t-apply-7.expect -rw-r--r-- 292 bytes
t-apply-7.patch -rw-r--r-- 12.0 KB

back to top