


Some of the other remotes have more sophisticated multipart uploads where you can upload the parts in parallel, but I don't think that is possible with dropbox. Note that it will use 128M for each transfer in progress potentially - so just try this on your 16GB file to start with. Try it bigger and smaller too if it is easy. Or it could possibly be dropbox processing the chunk.Ĭan you try -buffer-size 128M - this should let the buffer get 1 upload chunk ahead. I think what is happening with the chunked uploads is that rclone is reading a chunk off disk then uploading it, so the pause is the read off disk bit. That's like half the speed of the original client? Uploading the same file with rclone is fluctuating a lot like already discussed above and on average the speed is more like 3mbyte/sec (calculated, based on time & file size). On the other hand I did do some more tests with Dropbox original client and uploading files 10Gb in size is always about the same speed: about 8 - 9mbyte/sec on my network graphs. Or maybe it's something different as it's telling things like "rate limited". I'm just telling this because maybe this might be related to the initial problem discussed here. low level retry 1/10Ĥ 16:14:19 DEBUG : pacer: Reducing sleep to 15ms

While rclone is running I see messages like this:Ĥ 16:14:19 DEBUG : pacer: Rate limited, increasing sleep to 20msĤ 16:14:19 DEBUG : pacer: low level retry 1/1 (error too_many_write_operations/.)Ĥ 16:14:19 DEBUG : album/10036/26668/1515498.JPG: Received error: upload failed: too_many_write_operations/. Now, I'm not sure if this would be faster with the original Dropbox client, I never tested this.īut I can't easily test it either because the images are on a NAS and the original dropbox client has no support for that afaik.

Which is pretty slow and going to take a long time :( It's now uploading many many image files and it looks like it's only able to upload one picture per second at best. Uploading many files, instead of big ones, with rclone to dropbox.
