aboutsummaryrefslogtreecommitdiff
path: root/doc/scalability.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-02-15 14:34:40 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-02-15 14:34:40 -0400
commit4645f836781fd1db91c2b64138d441508a2bb847 (patch)
tree12e2c46545d5c911537ac82055e7e47d34481c72 /doc/scalability.mdwn
parentf0f07db01de13a6da8f0fd50532c5cb004e82d81 (diff)
add tips
Diffstat (limited to 'doc/scalability.mdwn')
-rw-r--r--doc/scalability.mdwn13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/scalability.mdwn b/doc/scalability.mdwn
index 71e21ac4c..232a84cc6 100644
--- a/doc/scalability.mdwn
+++ b/doc/scalability.mdwn
@@ -29,3 +29,16 @@ git-annex is designed for scalability. The key points are:
* It can use as much, or as little bandwidth as is available. In
particular, any interrupted file transfer can be resumed by git-annex.
+
+## scalability tips
+
+* If the files are so big that checksumming becomes a bottleneck, consider
+ using the [[WORM_backend|backends]]. You can always `git annex migrate`
+ files to a checksumming backend later on.
+
+* If you're adding a huge number of files at once (hundreds of thousands),
+ you'll soon notice that git-annex periodically stops and say
+ "Recording state in git" while it runs a `git add` command that
+ becomes increasingly expensive. Consider adjusting the `annex.queuesize`
+ to a higher value, at the expense of it using more memory.
+