4 ms·
There are other considerations with Windows as well - if you’re using SMB, large file counts in a directory will create performance issues with SMB shares.
by Spooky23 5y ago
There are other considerations with Windows as well - if you’re using SMB, large file counts in a directory will create performance issues with SMB shares.
- magicalhippo 5y agoMaybe you're referring to something else, but what I noticed was due to case sensitivity. Turning off case sensitivity lead to orders of magnitude difference in directory performance, and since most applications just use what they get from the system for filenames, there's very few problems in practice. My main machines are all Windows and I've been running my NAS with case sensitivity off for almost a decade now, and only a few times did I have to manually rename some file through the NAS (two files with same name but different case). I use my NAS actively for a lot of things, including sharing files across my machines.
- southerntofu 5y ago> Turning off case sensitivity lead to orders of magnitude difference in directory performance What filesystem are you using? I assume case-insensitivity means your filesystem does not support UTF-8 filenames. Is that the case?
- zaarn 5y agoNo, case insensitive just means that the filesystem considers uppercase letters and lowercase letters to be the same. You have to be Unicode (or character set) aware for that. You can set ZFS and in newer Linux Kernels for a filesystem to be case insensitive, and neither really cares about UTF8 to begin with as long as the filename contains no NUL characters. Windows only requires the filename to be somewhat valid UCS-2 (ie, UTF-16 with the safeties off) on NTFS, FAT does the same for ASCII (though nothing stops a kernel from putting UTF8 in a FAT filename.
- southerntofu 5y ago> No, case insensitive just means that the filesystem considers uppercase letters and lowercase letters to be the same. You have to be Unicode (or character set) aware for that. I assumed in your case that meant ASCII encoding, but i still don't understand how turning off case sensitivity would speed up things. Was that a typo, or am i missing something? > nothing stops a kernel from putting UTF8 in a FAT filename Except interoperability with other systems who may access this filesystem of course. Thanks for this explanation.
- magicalhippo 5y ago> i still don't understand how turning off case sensitivity would speed up things. Maybe it's very Samba specific, but when doing a directory listing on a case-insensitive SMB share it parses the entire directory first before returning the first result. I forgot the exact reason why, maybe to resolve conflicts, say "foo.txt" and "FOO.txt" can only have one entry. Regardless, the result is a massive initial delay. Marking the share as case-sensitive skips all this. Worked wonders for me anyway. Also, when creating "Foo.txt" on a case-insensitive share, it has to check that it doesn't collide with any existing file with different case, etc.
- southerntofu 5y agoThat's also my understanding, but your initial comment suggested that turning off case-sensitivity sped things up. Sorry for the misunderstanding!