diff options
Diffstat (limited to 'path-spec.txt')
| -rw-r--r-- | path-spec.txt | 24 |
1 files changed, 17 insertions, 7 deletions
diff --git a/path-spec.txt b/path-spec.txt index b1c9fde..33d50e5 100644 --- a/path-spec.txt +++ b/path-spec.txt @@ -183,7 +183,7 @@ Tables of Contents (F is as above.) * Having a descriptor for every one of the first - NUM_GUARDS_TO_USE guards among our primary guards. (see + NUM_USABLE_PRIMARY_GUARDS guards among our primary guards. (see guard-spec.txt) We define the "fraction of bandwidth-weighted paths" as the product of @@ -192,7 +192,7 @@ Tables of Contents * The fraction of descriptors that we have for nodes with the Guard flag, weighted by their bandwidth for the guard position. * The fraction of descriptors that we have for all nodes, - weighted by their bandwidth for the middle position position. + weighted by their bandwidth for the middle position. * The fraction of descriptors that we have for nodes with the Exit flag, weighted by their bandwidth for the exit position. @@ -491,7 +491,7 @@ Tables of Contents used directly as Xm. Instead of using the mode of discrete build times directly, Tor clients - compute the Xm parameter using the weighted average of the the midpoints + compute the Xm parameter using the weighted average of the midpoints of the 'cbtnummodes' (10) most frequently occurring 10ms histogram bins. Ties are broken in favor of earlier bins (that is, in favor of bins corresponding to shorter build times). @@ -511,7 +511,7 @@ Tables of Contents All times below Xm are counted as having the Xm value via the MAX(), because in Pareto estimators, Xm is supposed to be the lowest value. - However, since clients use mode averaging to estimatre Xm, there can be + However, since clients use mode averaging to estimate Xm, there can be values below our Xm. Effectively, the Pareto estimator then treats that everything smaller than Xm happened at Xm. One can also see that if clients did not do this, alpha could underflow to become negative, which @@ -577,7 +577,7 @@ Tables of Contents to the point 'cbtclosequantile' (default 99) on the Pareto curve, or 60 seconds, whichever is greater. - The actual completion times for these measurements circuits should be + The actual completion times for these measurement circuits should be recorded. Implementations should completely abandon a circuit and ignore the circuit @@ -633,8 +633,8 @@ Tables of Contents Default: 20 Min: 3 Max: 1000 - Effect: This is the number of circuit build times to keep track of - for the following option. + Effect: This is the number of circuit build outcomes (success vs + timeout) to keep track of for the following option. cbtmaxtimeouts Default: 18 @@ -644,6 +644,10 @@ Tables of Contents circuit attempts, the client should discard all of its history and begin learning a fresh timeout value. + Note that if this parameter's value is greater than the value + of 'cbtrecentcount', then the history will never be + discarded because of this feature. + cbtmincircs Default: 100 Min: 1 @@ -651,6 +655,12 @@ Tables of Contents Effect: This is the minimum number of circuits to build before computing a timeout. + Note that if this parameter's value is higher than 1000 (the + number of time observations that a client keeps in its + circular buffer), circuit build timeout calculation is + effectively disabled, and the default timeouts are used + indefinitely. + cbtquantile Default: 80 Min: 10 |