Martin Fick <mfick@xxxxxxxxxxxxxx> writes: > After a gc, the repo does perform the similar to the > uncompressed one (which was achieved via gc). After gc, it > takes ~.05s do to a 'git branch' with 1.7.6 and > git.1.7.7.rc0.72.g4b5ea. It also takes a bit more than 15s > with the patch reverted. So it appears that compression is > not likely the culprit, but rather the need to be gced. Isn't packing refs part of "gc" these days? -- 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