summaryrefslogtreecommitdiff
path: root/doc/bird.sgml
diff options
context:
space:
mode:
authorMaria Matejka <mq@ucw.cz>2022-07-10 14:19:24 +0200
committerMaria Matejka <mq@ucw.cz>2022-07-10 14:19:24 +0200
commit7e9cede1fd1878fb4c00e793bccd0ca6c18ad452 (patch)
treea61f837bcbda9aac2c6278d6f3e256e17b41aac3 /doc/bird.sgml
parent652be92a21f5575e5f74f6abe98eb4200b86776c (diff)
parentb867c798c3e42c875311a79fe53a36d4a5bfd126 (diff)
Merge version 2.0.10 into backport
Diffstat (limited to 'doc/bird.sgml')
-rw-r--r--doc/bird.sgml15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/bird.sgml b/doc/bird.sgml
index 467024bc..3862fa10 100644
--- a/doc/bird.sgml
+++ b/doc/bird.sgml
@@ -684,6 +684,21 @@ to set options.
limit to the settle time from the initial ROA table change even if
there are consecutive updates gradually renewing the settle time.
Default: 20 s.
+
+ <tag><label id="rtable-gc-threshold">gc threshold <m/number/</tag>
+ Specify a minimum amount of removed networks that triggers a garbage
+ collection (GC) cycle. Default: 1000.
+
+ <tag><label id="rtable-gc-period">gc period <m/time/</tag>
+ Specify a period of time between consecutive GC cycles. When there is a
+ significant amount of route withdraws, GC cycles are executed repeatedly
+ with given period time (with some random factor). When there is just
+ small amount of changes, GC cycles are not executed. In extensive route
+ server setups, running GC on hundreds of full BGP routing tables can
+ take significant amount of time, therefore they should use higher GC
+ periods. Default: adaptive, based on number of routing tables in the
+ configuration. From 10 s (with <= 25 routing tables) up to 600 s (with
+ >= 1500 routing tables).
</descrip>