aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Mattt <Mattt@web>2015-06-30 03:10:26 +0000
committerGravatar admin <admin@branchable.com>2015-06-30 03:10:26 +0000
commit6e1c87a2396e7ef6fd04b6cccdbe3bdc37206099 (patch)
tree5c0b2668059e19230c0db8db27e6383a47aa4070
parent10cb30f834e92515d17e49bec9556586adf838bb (diff)
-rw-r--r--doc/forum/How_big_can_a_git-annex_repo_get_and_still_be_reliable_and_fast__63__.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/How_big_can_a_git-annex_repo_get_and_still_be_reliable_and_fast__63__.mdwn b/doc/forum/How_big_can_a_git-annex_repo_get_and_still_be_reliable_and_fast__63__.mdwn
new file mode 100644
index 000000000..1349ad95e
--- /dev/null
+++ b/doc/forum/How_big_can_a_git-annex_repo_get_and_still_be_reliable_and_fast__63__.mdwn
@@ -0,0 +1,8 @@
+As title says, how big can a git-annex repo be?
+
+My use case is this:
+I have a few external hard disks (like 2TB, 3TB etc) and each of them have a bunch of files. Ideally I would like to keep all of the data organized in a _single_ git annex repo. However, there are probably a handful of really big files and a LARGE number of really small files, and I doubt its a good idea to put all of them in together.
+
+What should be my biggest concern? I assume file size is not a problem, and I should either tar/zip smaller files into much bigger ones and annex that, or split it up into multiple small annex repositories.
+
+Any suggestions? What do the rest of you with similar amounts of data do?