Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • rsync over network uses ssh by default. ssh cannot saturate fast networks, it is a long-standing problem. That's why compression is a requirement for network transfers with rsync over ssh. See unix.stackexchange.com/a/746573/29923 Commented May 21, 2023 at 23:32
  • @MaximEgorushkin The point I make in my answer is that if your system can't compress data fast enough (or if the destination system can't decompress the data fast enough), then compression will slow down the transfer. Likewise, compression will make no difference if the disks on either system are too busy and can't offer the throughput needed to read or write the data. Your argument is valid if you assume CPU and disk are not an issue and that these can handle the processing of data. Using a modified SSH implementation may be a further option if you support it with state-of-the-art hardware. Commented May 22, 2023 at 5:57