Re: [tor-bugs] #28519 [Core Tor/sbws]: Prioritize relays with no measured bandwidth in the consensus

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#28519: Prioritize relays with no measured bandwidth in the consensus
---------------------------+--------------------------
 Reporter:  juga           |          Owner:  (none)
     Type:  defect         |         Status:  new
 Priority:  Medium         |      Milestone:  sbws 1.1
Component:  Core Tor/sbws  |        Version:
 Severity:  Normal         |     Resolution:
 Keywords:                 |  Actual Points:
Parent ID:  #22453         |         Points:
 Reviewer:                 |        Sponsor:
---------------------------+--------------------------

Comment (by arma):

 It seems like the simple rule of "prioritize relays if we don't have
 enough recent measurements of them" should produce the behavior we want,
 right?

 Like, if the consensus doesn't have a measured number, but it's the fault
 of *other* scanners (e.g. because we're the only ones voting a number),
 then re-measuring it over and over ourselves isn't going to help anything.

 I'm trying to avoid the outcome where we need a full-page complex diagram
 to explain to people how sbws decides which relay to scan next. :) Some
 complexity is needed, but we should be trying to find ways to avoid adding
 complexity that we aren't sure we need.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28519#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs