summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joey.kitenet.net/ <joey@web>2011-03-14 16:12:51 +0000
committerGravatar admin <admin@branchable.com>2011-03-14 16:12:51 +0000
commit5e9f90240367e9b1006402fe776c24f2488876b2 (patch)
treeb84ea9fec50a86a4889c1cdf018e037104e7f21f
parent769d2a780d33fda9dd6e3b4242d31edf5ff2e232 (diff)
Added a comment
-rw-r--r--doc/forum/hashing_objects_directories/comment_2_d095c769febedca2d69fa5d099bcb520._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/forum/hashing_objects_directories/comment_2_d095c769febedca2d69fa5d099bcb520._comment b/doc/forum/hashing_objects_directories/comment_2_d095c769febedca2d69fa5d099bcb520._comment
new file mode 100644
index 000000000..41c6ad5d9
--- /dev/null
+++ b/doc/forum/hashing_objects_directories/comment_2_d095c769febedca2d69fa5d099bcb520._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="http://joey.kitenet.net/"
+ nickname="joey"
+ subject="comment 2"
+ date="2011-03-14T16:12:51Z"
+ content="""
+My experience is that modern filesystems are not going to have many issues with tens to hundreds of thousands of items in the directory. However, if a transition does happen for FAT support I will consider adding hashing. Although getting a good balanced hash in general without, say, checksumming the filename and taking part of the checksum, is difficult.
+
+I prefer to keep all the metadata in the filename, as this eases recovery if the files end up in lost+found. So while \"SHA/\" is a nice workaround for the FAT colon problem, I'll be doing something else. (What I'm not sure yet.)
+
+There is no point in creating unused hash directories on initialization. If anything, with a bad filesystem that just guarantees worst performance from the beginning..
+"""]]