Post #1566084
2026-04-23 06:22 UTC
Replies (4)
-
@HaraldKi@nrw.social 2026-04-23 06:36
@statsguy@mas.to Quick sanity check: pyrsync 13 commits total, last one 14 years ago. https://github.com/isislovecruft/pyrsync rsync 7800 commits total, last one yesterday https://github.com/rsyncproject/rsync Software which is just perfect and needs no mending and fixing all the time is absolutely fantastic. Yet I doubt prsync is in that league.😎 😀 (Whereby I am absolutely not implying rsync is bad because it has many commits. The above merely descibes a seemingly unattainable perfect state🙂 .)
-
@rayk@techhub.social 2026-04-23 06:39
@statsguy@mas.to Performance might vary a bit depending on whether there is a lot of data to transfer or not. Rsync hashes file chunks to avoid sending data when it’s not necessary, and the C version might perform slightly better for that. Otherwise the process is I/O bound, which should mean you get the roughly the same performance when there is a lot of data that needs to be transferred. Personally, I’d shell to rsync, but then I’d probably use a shell script instead of python as well, unless there is some other need for the capabilities that python provides.
-
@diazona@techhub.social 2026-04-23 06:51
@statsguy@mas.to In practice, no. Theoretically, starting up a separate process (e.g. to run rsync) places a slight extra burden on the system, but it's not going to make any noticeable difference unless you're doing this many thousands of times per second or something like that. There may also be differences in how fast the two pieces of software work, but again, it typically wouldn't matter, and if it does the only way to know is to test it. That is, assuming that both pieces of software properly do what they're supposed to do. As @HaraldKi@nrw.social mentioned, you can be a lot more confident that rsync does what it's supposed to do than you can that pyrsync does what it's supposed to do. So if you need reliability, that's a point in favor of rsync.
-
@paco@infosec.exchange 2026-04-24 03:15
@statsguy@mas.to Everybody is giving good guidance. But I don’t understand the question. Meaning: rsync does it and has tons of documentation and examples. Was there something that gave you pause and prompted you to consider alternatives? The difference in performance between Python or a binary are probably not going to be material. If the Python is written well, your waiting time will be spent waiting on I/O. It’s not a cpu-intensive activity.