summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-02-17 17:49:39 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-02-17 17:49:39 -0400
commitf5cb94fc03df60d220bae452bf3b611a6c718b02 (patch)
tree05c03d38c21c247a668a3e3726e5916d23f2a8d9
parent11b6c493890f232acac8c40de52c55493fa22c0c (diff)
comment
-rw-r--r--doc/forum/optimising_lookupkey/comment_1_e06db4754805c1e0ee298ecc676427d2._comment18
1 files changed, 18 insertions, 0 deletions
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 000000000..2b26d5e58
--- /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.
+"""]]