summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar https://id.koumbit.net/anarcat <https://id.koumbit.net/anarcat@web>2015-02-13 16:09:18 +0000
committerGravatar admin <admin@branchable.com>2015-02-13 16:09:18 +0000
commit309d05fa3f01388cc68ad5bdb627590802fed244 (patch)
tree49a8f059a7b499cf8baa83765231fab9dcbd9757 /doc
parent5c0254221e3425779b55df6718a6a789299121ed (diff)
add extra question about cat-file vs find
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/optimising_lookupkey.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/optimising_lookupkey.mdwn b/doc/forum/optimising_lookupkey.mdwn
index b8e4a0353..5a7da7383 100644
--- a/doc/forum/optimising_lookupkey.mdwn
+++ b/doc/forum/optimising_lookupkey.mdwn
@@ -2,4 +2,12 @@ to work around [[forum/original_filename_on_s3/]], i need to get the key from a
could i optimise this by simply doing a `readlink` call on the git checkout? it sure looks like `readlink | basename` is all I really need, and that can probably be done below 10ms (4ms in my tests). how reliable are those links anyways, and is that what lookupkey does?
+similarly, i wonder if it's safe to bypass git-annex and talk straight with git to extract location tracking? i can jump from 90ms to below 10ms for such requests if I turn `git annex find <file>` into the convoluted:
+
+<pre>
+git annex lookupkey $file
+printf $key | md5sum
+git cat-file -p refs/heads/git-annex:$hash/${key}.log
+</pre>
+
thanks. --[[anarcat]]