zstd VS rsync

Of course, you may get different results with another dataset.

gzip (zlib -6) [ratio=32%] [compr=35Mo/s] [dec=407Mo/s]

zstd (zstd -2) [ratio=32%] [compr=356Mo/s] [dec=1067Mo/s]

NB1: The default for zstd is -3, but the table only had -2. The difference is probably small. The range is 1-22 for zstd and 1-9 for gzip.

NB2: The default program for gzip (at least with Debian) is the executable from zlib. With my workflows, libdeflate-gzip iscompatible and noticably faster.

NB3: This benchmark is 2 years old. The latest releases of zstd are much better, see https://github.com/facebook/zstd/releases

For a high compression, according to this benchmark xz can do slightly better, if you're willing to pay a 10× penalty on decompression.

xz -9 [ratio=23%] [compr=2.6Mo/s] [dec=88Mo/s]

zstd -9 [ratio=23%] [compr=2.6Mo/s] [dec=88Mo/s]

Compression, synchronization and backup systems often use rolling hash to implement "content-defined chunking", an effective form of deduplication.

In optimized implementations, Rabin-Karp is likely to be the bottleneck. See for instance https://github.com/facebook/zstd/pull/2483 which replaces a Rabin-Karp variant by a >2x faster Gear-Hashing.

Get the data https://publicdistst.blob.core.windows.net/data/root.tar.zst magnet:?xt=urn:btih:84931cd80409ba6331f2fcfbe64ba64d4381aec5&dn=root.tar.zst How to extract https://github.com/facebook/zstd Linux (debian): `sudo apt install zstd` ``` tar -I 'zstd -d -T0' -xvf root.tar.zst ```

I've done that experiment with zstd before.

https://github.com/facebook/zstd/blob/dev/programs/zstd.1.md...

Not sure about brotli though.

If you want this functionality in zstd itself, check this out: https://github.com/facebook/zstd/pull/2349

The story says : "ZSTD 1.5.5 is released with a corruption fix found at Google"

rsync can be used to synchronize a local disk to the pCloud drive p. Works similarly as the Sync option of the pCloud Drive app. May be useful if one prefers a bulk upload once a day over a continuous synchronization.

Tools that can be used to handle this include Rsync, Duplicati, Cohesity

To overcome this issue, you can use rsync, a powerful command-line tool for synchronizing files and directories, along with a bash script that excludes the node_modules folder and also filter out anything in a .gitignore file that you specify. In this article, I'll guide you through the process of setting up and using this bash script to sync your Node.js project while ignoring the node_modules folder.

On OL9 I installed rsync using https://github.com/WayneD/rsync/blob/master/INSTALL.md and installing dependencies using the For Fedora 33 commands where possible except xxhash which wasn't found, so I used https://oraclelinux.pkgs.org/9/ol9-codeready-builder-aarch64/xxhash-devel-0.8.1-3.el9.aarch64.rpm.html

rsync will probably work better for this use case

I would prefer to use a revision control system, like git if keeping multiple versions of documents is important. Otherwise, if you don't find anything else to your liking, you could write your own scripts based on rsync with the clone-dest, detect-renamed, and detect-renamed-lax patches.

Give rsync a try, it should handle UTF filenames just fine.

While researching this issue I stumbled upon this thread where someone found out that a rsync 3.2.3 / glibc bug (github issue) leads to the error Operation not supported (95).\ my Proxmox instance is also using rsync 3.2.3: root@proxmox:~# rsync -V rsync version 3.2.3 protocol version 31 In this thread I found it's recommended to upgrade to another rsync version, but I'm not really sure how.\ \ Any thoughts on this?