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*
- 20Your type of data is also a major factor (factor #3 missing from the list). The linked article uses a typical mix of data. Yours might not be typical. If you are syncing 100% ZIP files (or any pre-compressed data) you probably don't want compression. If you are syncing 100% text files you might be faster to compress even if your network is fast and your CPU is slowish. Weigh all 3 factors.Richard Brightwell– Richard Brightwell2019-08-23 02:07:29 +00:00Commented Aug 23, 2019 at 2:07
- 2This is a great answer. That chart helps me thinking about this in ways I hadn't before.Graham P Heath– Graham P Heath2020-06-08 17:33:52 +00:00Commented Jun 8, 2020 at 17:33
- is this statement correct? -> "I use a 56k modem and have c64 cpu, therefore I should activate the rsync -z flag."kiltek– kiltek2022-12-08 16:05:28 +00:00Commented Dec 8, 2022 at 16:05
- @kiltek Commodore 64 chips are really, really slow though.. maybe try benchmarking and report back here? I, too, would like to know.aggregate1166877– aggregate11668772023-04-25 04:28:34 +00:00Commented Apr 25, 2023 at 4:28
- 2@Lou "It really depends" and it's not that hard to grok. Compression takes CPU time. CPU time that could have been spent sending uncompressed data. Spending that CPU time on compression is basically only worth it if both the link is slower-ish and your CPU's not too slow.Petr Skocik– Petr Skocik2023-11-23 22:17:09 +00:00Commented Nov 23, 2023 at 22:17
| Show 3 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. shell-script), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you