Rclone throughput degradation with swift

We observed a throughput degradation with swift versions 1.61 - 1.69 (those two versions tested heavily, observed the degradation) compared to 1.42 - 1.48 (those two versions tested heavily without observed degradation).

At the same time replications into S3 buckets worked as expected, without any throughput impact.

The solution is the workaround, replication into swift targets are managed with rclone version 1.48 and replications into S3 buckets with 1.61 or 1.69 .

Are you aware of this behaviour?

Regards

welcome to the forum,

when you posted, there should have been a template of questions for you to answer??

sorry for not being compliant in the format.
The summary of the observed throughput is here:

rclone version source target: remote swift
/usr/bin/rclone.1.42 local file (nfs) 7-8 M/s
/usr/bin/rclone.1.48 local file (nfs) 7-8 M/s
/usr/bin/rclone.1.61 local file (nfs) 170-220 K/s
/usr/bin/rclone.1.69.1 local file (nfs) 170-220 K/s

The version details:
"/usr/bin/rclone.1.42 --version
rclone v1.42

  • os/arch: linux/amd64
  • go version: go1.10.3"

"/usr/bin/rclone.1.48 --version
rclone v1.48.0

  • os/arch: linux/amd64
  • go version: go1.12.6"

"/usr/bin/rclone.1.61--version
rclone v1.61.1-DEV

  • os/version: sles 15-SP3 (64 bit)
  • os/kernel: 5.3.18-150300.59.161-default (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.18.9
  • go/linking: dynamic
  • go/tags: none"

" /usr/bin/rclone.1.69.1 --version
rclone v1.69.1

  • os/version: sles 15.3 (64 bit)
  • os/kernel: 5.3.18-150300.59.191-default (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.24.0
  • go/linking: static
  • go/tags: none"

the used config:
[$aRemoteRegion]
type = swift
user = aUser
key = aKey
auth = https://identity-3.${aRegion}.cloud.sap:443/v3
domain = $aDomain
tenant = $aTenant
tenant_domain = aDomain
region = $aRemoteRegion
auth_version = 3

the used command example:
rclone copyto /var/crash/tFile.bin $aRemoreRegion:SUSE_TMP/t_20250219.1 --config $cnf --swift-chunk-size 512m --log-level DEBUG --log-file rclone-trace_${stamp}

the question:
are you aware of this behavior?
Are probably additional setting needed?

perhaps replication is done server-side, as compared to rclone copyto command is not.


need full, complete debug logs, with the exact commands.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.