![]() Above that threshold however, Explorer's transfer rate plummets. Below some threshold (thousands of files), transfers happen efficiently. ![]() Even if Windows is doing multiple IO to the MFT or whatever (surely this is cached when doing a perfectly predictable batch write operation?), that'd still only be a relatively small overhead relative to the size of the write.įWIW, I've seen this happen many times on moving image files in Windows. 571000/45795 = 12.5 MB per file = thousands of sectors per file. For large files, the seeking is over and a nice, fast, long, sequential write operation can take place. For small files, this means it's just a shitload of seeking. ![]() A write needs to be made to the directory file, sometimes to the MFT, then the write of the actual file has to take place, then another write to the directory file. Small files involve the same filesystem overhead as large files. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |