[tor-bugs] #33947 [Core Tor/sbws]: Compare sbws and Torflow
Tor Bug Tracker & Wiki
blackhole at torproject.org
Tue Apr 21 15:02:03 UTC 2020
#33947: Compare sbws and Torflow
-------------------------------+-------------------------------
Reporter: juga | Owner: (none)
Type: defect | Status: new
Priority: Medium | Milestone: sbws: 1.1.x-final
Component: Core Tor/sbws | Version: sbws: 1.1.0
Severity: Normal | Keywords: sbws-roadmap
Actual Points: | Parent ID: #33121
Points: | Reviewer:
Sponsor: |
-------------------------------+-------------------------------
gk and i were talking about what to review in #30375 and we thought it'd
be useful to create a ticket to check whether the bugfixes we have been
working on (https://trac.torproject.org/projects/tor/query?keywords=~sbws-
roadmap&status=closed) to deploy sbws in all bwauths are working, ie.
making sbws to behave very close to Torflow.
I think we should document what to check, where/how to check it and which
ticket(s) intended to fix it.
I also think we should add this as documentation in sbws itself because
they're important questions that have been blockers to deploy sbws in all
bwauths and to avoid regressions in the future.
Some of the main things to check that should be further explained are:
- whether sbws "failures" "low" (#30719)
- whether the number of relays to vote on reported by sbws "similar" to
the number of relays reported by torflow (#30727, #30735)
- whether sbws relay descriptors are updated (#30733)
- whether sbws router statuses (relay info. from consensus) are updated
(#30733)
- whether sbws consensus bandwidth total sum is similar to torflow
(#33871, #33009, #33350)?
- whether changes in a relay consensus bandwidth affect in a similar way
as torflow (#33871)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33947>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list