Copying 59 GiB over a 10 Gbps network took more than 8 minutes with rsync, while rclone finished the same copy in about 2 minutes. You may think rsync is the gold standard for file sync on Linux, until you watch your network graph stall far below capacity during a backup or a big storage migration. The problem is not the network, it is that rsync copies files one at a time, in sequence. Knowing when to stay with rsync and when to switch to rclone can cut your sync time several times over without changing any infrastructure.

What Jeff Geerling measured

The numbers above come from Jeff Geerling's post (May 6, 2025). He copied about 59 GiB, more than 3,500 files with dozens of them 1 to 10 GB each, from an NVMe-backed NAS mounted on a Mac to a Thunderbolt SSD over a 10 Gbps network.

  • rsync -au: about 8 minutes 17 seconds. Transfer topped out around 350 MB/s because files are copied one at a time.
  • rclone sync with --multi-thread-streams=32: about 2 minutes 15 seconds, with the network fully used at roughly 1 GB/s.
  • When only a couple of files changed, both were nearly equally fast. Scanning the directory tree took about the same time (around 18 seconds), so rclone's edge comes from parallel transfers, not from scanning.

That is one setup. Your hardware, file sizes, and network may give different numbers, so test with your own data before deciding.

When to use rsync

Pick rsync when precision at the Linux filesystem level matters, and when files change only partially.

  • Syncing between Linux servers over SSH. A good fit for source code, config in /etc, or application directories where file permissions are critical.
  • Full POSIX metadata. -a keeps permissions, owner, group, symlinks, and timestamps. Add -H for hardlinks, -A for ACLs, and -X for extended attributes, since -a alone covers none of them.
  • Large files with small changes. The delta-transfer algorithm sends only the parts that changed, for example in log files, database dumps, or disk images. It works for transfers over the network (SSH or daemon). For copies between local paths, including already-mounted shares, rsync generally copies whole files.
  • Limited bandwidth. Delta-transfer and compression save data on slow links.
rsync -aHAX --info=progress2 user@server:/data/ /backup/data/

When to use rclone

Pick rclone when parallel transfer speed is the priority, or when your target is cloud or object storage.

  • Fast network and large files. --multi-thread-streams splits the transfer of one large file into several streams, so 10 Gbps of bandwidth actually gets used.
  • Lots of files at once. --transfers runs several file transfers at the same time and --checkers checks several files in parallel. Both are worth trying for thousands of files, but you should measure the best values yourself.
  • Cloud and object storage. rclone supports dozens of providers: Amazon S3, Cloudflare R2, Google Drive, Backblaze B2, MinIO, up to SFTP and SMB.
  • Client-side encryption. The crypt feature encrypts file names and contents before uploading to external storage.
rclone sync /Volumes/nas/ /Volumes/ssd/projects \
  --multi-thread-streams=32 \
  --backup-dir /Volumes/ssd/rclone_backups/$(date +%Y-%m-%d_%H-%M-%S) \
  --links --metadata -P
rclone copy /data/ s3remote:bucket/data --transfers=16 --checkers=32 -P

Two safety notes before running rclone sync. First, it makes the destination match the source exactly, meaning files missing from the source get deleted at the destination. --backup-dir moves would-be-deleted files into a backup directory, and --dry-run shows what would happen without changing anything. Second, rclone re-uploads the whole of any changed file, not just the differing parts like rsync's delta-transfer.

Quick comparison

Needrsyncrclone
Keep Linux permissions, owners, and symlinksVery complete (-aHAX)Partly, via --metadata and --links
Many files or large files on a fast networkSequential, one file at a timeParallel and multi-stream
Large file with small changes over a networkDelta-transferRe-uploads the whole file
S3, R2, Google Drive, or BackblazeNot supported directlyBuilt in
Between Linux servers over SSHThe standard choicePossible via the SFTP backend

Conclusion

There is no absolute winner. Use rsync for precise syncs between Linux systems and for files that change a little. Switch to rclone when your network is fast but your copy is slow, or when your destination is cloud storage. If in doubt, run both on a test directory with time and see for yourself.

References