You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a 1Gbps network environment, I'm using rclone copy files from a NFS-mounted directory to a Ceph S3 bucket. The speed is only around 35MB/s. However, when I mount the Ceph S3 bucket to the same client machine as an NFS directory and use cp directly to copy files, the speed is approximately 90MB/s. And use rclone copy a local dir file to Ceph S3 bucket, the speed is also approximately 70MB/s.
What is your rclone version (output from rclone version)
--s3-upload-concurrency int Concurrency for multipart uploads and copies (default 4)
--s3-chunk-size SizeSuffix Chunk size to use for uploading (default 5Mi)
Making them larger will help a lot at the cost of more memory usage.
--s3-upload-concurrency int Concurrency for multipart uploads and copies (default 4)
--s3-chunk-size SizeSuffix Chunk size to use for uploading (default 5Mi)
Making them larger will help a lot at the cost of more memory usage.
The associated forum post URL from
https://forum.rclone.org
https://forum.rclone.org/t/poor-copy-sync-speed-from-a-nfs-mounted-directory-to-ceph-s3-bucket/45912
What is the problem you are having with rclone?
In a 1Gbps network environment, I'm using
rclone copy
files from a NFS-mounted directory to a Ceph S3 bucket. The speed is only around 35MB/s. However, when I mount the Ceph S3 bucket to the same client machine as an NFS directory and usecp
directly to copy files, the speed is approximately 90MB/s. And userclone copy
a local dir file to Ceph S3 bucket, the speed is also approximately 70MB/s.What is your rclone version (output from
rclone version
)rclone v1.66.0
Which OS you are using and how many bits?
Centos 8 Stream 64bit aarch64
Which cloud storage system are you using?
Ceph S3
The command you were trying to run
A log from the command with the
-vv
flagHow to use GitHub
The text was updated successfully, but these errors were encountered: