From b62bb3b1a8d77def6cdfe5ccf221758a50ed5719 Mon Sep 17 00:00:00 2001 From: Axel Burri Date: Fri, 3 May 2019 15:35:25 +0200 Subject: [PATCH] btrbk: get_related_readonly_nodes: vastly increase abort_distance It's not uncommon to have a large intact parent-chain on targets (e.g. target_preserve_min=all). If this is the case, performance drops a bit on "btrbk archive". Note that we could limit the search depth in get_best_parent() for some performance improvements, as this only affects extra clones. --- btrbk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/btrbk b/btrbk index 1114478..1cd7845 100755 --- a/btrbk +++ b/btrbk @@ -3139,7 +3139,7 @@ sub get_related_readonly_nodes($;@) my $parent_uuid_hash = $vol->{node}{TREE_ROOT}{PARENT_UUID_HASH}; my $node = $vol->{node}; my $uuid = $node->{uuid}; - my $abort_distance = 256; + my $abort_distance = 4096; # climb up parent chain my $distance = 0; # parent distance