there is no hard line.
tho, at some point, there is a soft limit, and increasing transfers will not make a practical difference on transfer speed.
fwiw, establish a baseline, using default values, see that the overall transfer speed is as compared to an internet speed test.
also each backend is different. as gdrive limits the number of transfers per second.
could increase chunk size.
Thanks!
I wanted to know, since I intend to run this command frequently in order to keep my files in constant sync, is it correct to use --modify-window 1s
If I understand correctly according to the documentation, it checks how much time difference there is between my file and the file in the cloud?
I guess it's not the safest to do that but what could be the worst case scenario? Will this cause duplication?
Is there a faster method than checksums and can it be considered safe?
For small files Google Drive will only create 2-3 files per second regardless of --transfers value. Setting it higher than your backend can handle often leads to overall slower operations - as things will be throttled and retried.
I think with this particular provider even default values might be too high. Run tests with -vv flag and adjust accordingly.
Won't this result in the calculation of all the checksums and their comparison between the computer and the remote?
checksums take a long time to calculate for a large number of files don't they?
Haha yeah that's my typo, I guess that's the best I'll get for Google Drive cloud encrypted sync, no?
Is there anything better for such a purpose?
--max-age Duration Only transfer files younger than this in s or suffix ms|s|m|h|d|w|M|y (default off)
Is it lower than the age they were synced?
It is not so clear to me /:
no,
by default, rclone compares size and modtime only, not checksum. so that is quick.
if a file is transferred, then rclone compares the checksums, which with gdrive, takes no time.
yes, it is very confusing.
in other words, if a source file's modtime is 24 hours old or newer, then compare that source file to the dest file.
By the way, I wanted to ask, is there any limit on the amount of checkers I can put?
I assume it would be an Input Output limitation of my drive rather than the server side?
There is no strict limit imposed by rclone. However if you set it too high than you will kill either local IO or remote limits - or both. Only way to find optimal value is to run few tests. For your remote (Google drive) probably the best idea is to use defaults as it is known to apply very aggressive throttling if you try to abuse it.
no limit, but as i pointed out with transfers, increasing checks beyond a certain value, not yield improvements and could slow down the overall transfers.
it depends on the storage provider, your internet and your machine.
just have to do some basic testing, then you will know what works for you.