4 ms·
Maybe it's for people annoyed at Explorer taking upwards of 30 seconds to display folders with lots of files in them.
by opencl 7y ago
Maybe it's for people annoyed at Explorer taking upwards of 30 seconds to display folders with lots of files in them.
- naikrovek 7y agoI have a single folder (no subfolders) with 650,000 files in it, and the Win10 explorer is plenty fast if nothing in that folder is currently changing. Even if a single file access time changes it will spend 20-30 minutes trying to display the change, despite the access time not being displayed for any file. If you open the folder 1 second after the file access time is updated, it's instantaneous, as before. There's good and bad here. NTFS is a HELL of a lot better at handling stupid amounts of files in a folder like this than it used to be. But maybe it could handle a single file attribute change without losing its kind for 30 minutes.
- aargh_aargh 7y agoMaybe the problem is storing so many files all in one directory? /me ducks
- ygra 7y agoNTFS with default settings will actually degrade a fair bit on such a folder. You probably have to disable 8.3 legacy filename generation to make this work (or the usual pattern of using the file name prefix as folder names beneath that folder).