update
@ -32,6 +32,14 @@ You can make zfs-autobackup use less commands per snapshot transfer by:
|
||||
* `--no-holds`: to prevent the hold/release commands.
|
||||
* `--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
|
||||
|
||||
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.
|
||||
|
||||
NOTE: There is actually a performance regression in ZFS version 2: https://github.com/openzfs/zfs/issues/11560 Use --no-progress as workaround.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user