Rclone fails to switch to multi-part uploads when a file is too large

[ncw (Nick Craig-Wood)]

If you don't want slow to start you need --s3-disable-checksum

Hmm, things to try

Try setting --s3-upload-cutoff 1T (very large) so that you only upload files with single part uploads - does that help?

Also try --s3-concurrency 2

Related threads

How to maximize single file multipart upload speed to Cloudflare R2 (S3 compatible)

I did some brief testing to see what settings would get optimal upload speeds with RClone, and the following worked quite well, getting me over 1600 MB/s (megabytes, not megabits) with peaks over 2 GB/s. rclone copy -P --transfers 300 --s3-upload-concurrency 300 --s3-chunk-size 50M --no-check-dest --ignore-checksum --s3-disable-checksum ./testfile r2:mybucket Transferred: 30 GiB / 30 GiB, 100%, 1.648 GiB/s, ETA 0s Transferred: 1 / 1, 100% Elapsed time: 18.3s Asid…

Uploading large files to R2 (~ 250 MiB) with rclone causes signature errors

I ran the command: head -c 1G </dev/urandom > tempfile rclone copy tempfile r2:/temp2 -vv --retries 1 --low-level-retries 1 --dump responses 2>&1 | tee rclone.log Here's the output: 2022/09/28 21:47:06 DEBUG : rclone: Version "v1.59.2" starting with parameters ["rclone" "copy" "tempfile" "r2:/temp2" "-vv" "--retries" "1" "--low-level-retries" "1" "--dump" "responses"] 2022/09/28 21:47:06 DEBUG : Creating backend with remote "tempfile" 2022/09/28 21:47:06 DEBUG : Using config file from "/home/…

I suspect this is caused by some new rate limit at cloudflare - remember R2 is a relatively new service and we've seen quite a few changes in how it works over its brief life.