summaryrefslogtreecommitdiff
path: root/http-backend.c
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2012-01-06 14:17:40 -0500
committerJunio C Hamano <gitster@pobox.com>2012-01-06 13:28:55 -0800
commit926f1dd95486b596de1f6b8e108053a870da0e18 (patch)
tree02a1cc71b9feaa81356e71ffe0afc5d4f0997c8c /http-backend.c
parentccdc6037fee8761db82ccb8751d9c9442f4a9cc7 (diff)
downloadgit-926f1dd95486b596de1f6b8e108053a870da0e18.tar.gz
upload-pack: avoid parsing objects during ref advertisement
When we advertise a ref, the first thing we do is parse the pointed-to object. This gives us two things: 1. a "struct object" we can use to store flags 2. the type of the object, so we know whether we need to dereference it as a tag Instead, we can just use lookup_unknown_object to get an object struct, and then fill in just the type field using sha1_object_info (which, in the case of packed files, can find the information without actually inflating the object data). This can save time if you have a large number of refs, and the client isn't actually going to request those refs (e.g., because most of them are already up-to-date). The downside is that we are no longer verifying objects that we advertise by fully parsing them (however, we do still know we actually have them, because sha1_object_info must find them to get the type). While we might fail to detect a corrupt object here, if the client actually fetches the object, we will parse (and verify) it then. On a repository with 120K refs, the advertisement portion of upload-pack goes from ~3.4s to 3.2s (the failure to speed up more is largely due to the fact that most of these refs are tags, which need dereferenced to find the tag destination anyway). Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'http-backend.c')
0 files changed, 0 insertions, 0 deletions