[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [torspec/main] Clarify Xm tiebreaker rules.
commit 2b92f992ef27ceea3b253a3940a6da3127a0a8b8
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date: Fri Aug 27 10:48:43 2021 -0400
Clarify Xm tiebreaker rules.
---
path-spec.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/path-spec.txt b/path-spec.txt
index 77368d8..f257e86 100644
--- a/path-spec.txt
+++ b/path-spec.txt
@@ -449,7 +449,8 @@ of their choices.
Instead of using the mode of discrete build times directly, Tor clients
compute the Xm parameter using the weighted average of the the midpoints
of the 'cbtnummodes' (10) most frequently occurring 10ms histogram bins.
- Ties are broken in favor of earlier bins.
+ Ties are broken in favor of earlier bins (that is, in favor of bins
+ corresponding to shorter build times).
(The use of 10 modes was found to minimize error from the selected
cbtquantile, with 10ms bins for quantiles 60-80, compared to many other
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits