patrick/zfs_autobackup
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update

Edwin Eefting
2022-01-07 12:42:53 +01:00
parent 9d7d78d5da
commit 9c9a59d932
1 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
Performance.md

@ -32,6 +32,14 @@ You can make zfs-autobackup use less commands per snapshot transfer by:
* `--no-holds`: to prevent the hold/release commands. * `--no-holds`: to prevent the hold/release commands.
* `--allow-empty`: to prevent commands to figure out if a snapshot would be empty. * `--allow-empty`: to prevent commands to figure out if a snapshot would be empty.
## Disable progress (ZFS bug)
There is actually a performance regression in ZFS version 2: https://github.com/openzfs/zfs/issues/11560
This will make it so that each transfer takes approx 1 second extra. This is a problem if you have lots of tiny transfers.
Use --no-progress as workaround.
## Some statistics ## Some statistics
To get some idea of how fast zfs-autobackup is, I did some test on my laptop, with a SKHynix_HFS512GD9TNI-L2B0B disk. I'm using zfs 2.0.2. To get some idea of how fast zfs-autobackup is, I did some test on my laptop, with a SKHynix_HFS512GD9TNI-L2B0B disk. I'm using zfs 2.0.2.
@ -46,5 +54,4 @@ To be bold I created 2500 datasets, but that also was no problem. So it seems it
If you need more performance let me know. If you need more performance let me know.
NOTE: There is actually a performance regression in ZFS version 2: https://github.com/openzfs/zfs/issues/11560 Use --no-progress as workaround.