From 9c9a59d932a23a8b4e7ec077dce75b40ee5b6421 Mon Sep 17 00:00:00 2001 From: Edwin Eefting Date: Fri, 7 Jan 2022 12:42:53 +0100 Subject: [PATCH] update --- Performance.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/Performance.md b/Performance.md index ea6bd7f..25fd76a 100644 --- a/Performance.md +++ b/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. * `--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.