From 12e47e5760e996a75e22bb9276a8652cce3a36b1 Mon Sep 17 00:00:00 2001 From: Ed Hennis Date: Fri, 3 Feb 2023 08:42:46 -0800 Subject: [PATCH] Update documented pathfinding configuration defaults: * Add recommended values for node which want to support "advanced" pathfinding, which is effectively the old default behavior. --- cfg/rippled-example.cfg | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/cfg/rippled-example.cfg b/cfg/rippled-example.cfg index fda1671e416..02ef02e920f 100644 --- a/cfg/rippled-example.cfg +++ b/cfg/rippled-example.cfg @@ -758,7 +758,9 @@ # When searching for paths, the default search aggressiveness. This can take # exponentially more resources as the size is increased. # -# The default is: 7 +# The recommended value to support advanced pathfinding is: 7 +# +# The default is: 2 # # [path_search_fast] # [path_search_max] @@ -767,12 +769,19 @@ # If you do not need pathfinding, you can set path_search_max to zero to # disable it and avoid some expensive bookkeeping. # -# The default for 'path_search_fast' is 2. The default for 'path_search_max' is 10. +# To support advanced pathfinding the recommended value for +# 'path_search_fast' is 2, and for 'path_search_max' is 10. +# +# The default for 'path_search_fast' is 2. The default for 'path_search_max' is 3. # # [path_search_old] # # For clients that use the legacy path finding interfaces, the search -# aggressiveness to use. The default is 7. +# aggressiveness to use. +# +# The recommended value to support advanced pathfinding is: 7. +# +# The default is: 2 # # #