From 6154cbf4aa4d00c4dcfa7182396c86d5039c593a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 17 Feb 2015 17:49:39 -0400 Subject: [PATCH] comment --- ...1_e06db4754805c1e0ee298ecc676427d2._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/forum/optimising_lookupkey/comment_1_e06db4754805c1e0ee298ecc676427d2._comment diff --git a/doc/forum/optimising_lookupkey/comment_1_e06db4754805c1e0ee298ecc676427d2._comment b/doc/forum/optimising_lookupkey/comment_1_e06db4754805c1e0ee298ecc676427d2._comment new file mode 100644 index 0000000000..2b26d5e58b --- /dev/null +++ b/doc/forum/optimising_lookupkey/comment_1_e06db4754805c1e0ee298ecc676427d2._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-02-17T21:46:01Z" + content=""" +Yes, that's the same, except lookupkey only operates on files that are +checked into git. + +(Also, lookupkey will work in a direct mode repo, while such a repo +may not have a symlink to examine.) + +25ms doesn't seem bad for a "whole runtime" to fire up. :) I think most of +the overhead probably involves reading the git config and running +git-ls-files. + +Note that lookupkey can be passed a whole set of files, so you could avoid +the startup overhead that way too. +"""]]