Wait for the first thousands files to be copied.Operating system and version: Windows 10 64 bits with latest updates.I had to use -thread-count 5000 -timeout 100000 to reduce "insufficient resources" errors when accessing vault with lots of files.Īlso, despite the vault being created in a Google Shared Drive I don't think it's responsible for the delay because the files being copied are synchronized way before a new file starts to copy to the vault.Īlso doesn't matter if copying with windows explorer or robocopy command line tool. But each file takes a long time to start being copied.
Note that once the file starts being copied it's a fast transfer. I separated my data in several vaults, but it's the second vault I needed to create in this conditions and takes more than 3 days to copy 25000 files (average of files is 2 MB) because there's a delay of almost half a minute before each file even with files of a few KB.
First reading and listing the files in the vault (but that's expected) and then before every file it's being copied. When creating a vault with a large number of files (like more than 10,000), the first thousands of files are copied as fast as expected, but as the number of files in the vault grow there's a pause before each file (doesn't matter the size of the file) and that pause is increasing as the number of files in the vault increases.Įven if I restart the computer, when resuming copying takes a loooong time. (This is more a design problem than a bug, but very problematic.) Description
0 kommentar(er)
