[tor-bugs] #22453 [Core Tor/Tor]: Relays should regularly do a larger bandwidth self-test
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Nov 22 08:01:56 UTC 2018
#22453: Relays should regularly do a larger bandwidth self-test
-------------------------------------------------+-------------------------
Reporter: arma | Owner: juga
Type: defect | Status:
| needs_information
Priority: Medium | Milestone: Tor:
| unspecified
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: 034-triage-20180328, | Actual Points:
034-removed-20180328, tor-bwauth, |
035-backport, 034-backport-maybe, 033 |
-backport-maybe, 029-backport-maybe-not |
Parent ID: | Points:
Reviewer: teor | Sponsor:
-------------------------------------------------+-------------------------
Comment (by arma):
Replying to [comment:42 teor]:
> The important thing is that relays won't go backwards (like they
sometimes do with Torflow).
In terms of relay self-observation, we need to make sure they see load
(from real users or from bwauths) each day (more specifically, maybe it's
in the 24 hours before writing their descriptor) or they'll forget about
it.
That is, if we're trying to have a feedback cycle where we induce load,
the self-assessed number goes higher, and then we induce more load because
we see a higher number, then it's risky to let a day go by without hitting
the relay with at least that level of load. (I say 'risky', not 'bad',
because it could still turn out ok, either because some other scanner
induces that load, or because actual users show up and induce it.)
> Let's do this kind of optimisation in sbws 1.1.
Sounds like a great plan.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22453#comment:44>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list