[tor-bugs] #24104 [Core Tor/Tor]: Delay descriptor bandwidth reporting on large relays

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

#24104: Delay descriptor bandwidth reporting on large relays
------------------------------+-----------------------------------
     Reporter:  teor          |      Owner:  (none)
         Type:  defect        |     Status:  new
     Priority:  Medium        |  Milestone:  Tor: 0.3.3.x-final
    Component:  Core Tor/Tor  |    Version:
     Severity:  Normal        |   Keywords:  guard-discovery-stats
Actual Points:                |  Parent ID:
       Points:  1             |   Reviewer:
      Sponsor:                |
------------------------------+-----------------------------------
 In #23856, we:
 * reduced the bandwidth stats interval from 4 hours to 24 hours, and
 * reduced urgent (2x change) descriptor bandwidth reports from every 20
 minutes to every 3 hours.

 But we think we can make descriptor bandwidth reports even slower on large
 relays, because they have less need to ramp up their bandwidth.

 Here are our options:
 * don't report until the change is larger, for example, 4x
 * don't report for longer, for example, every 6 hours or 24 hours
 * delay the reporting of the *first* large change, as well as subsequent
 large changes

 Here are the open questions:
 * tor traffic has a daily cycle, so do we need to report large bandwidth
 changes multiple times a day to cope with this? (I think the answer is
 "no", because small changes are already reported every 18 hours on the
 standard descriptor schedule, and that seems to work fine. And large
 changes are already reported once, then the delay is imposed.)

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24104>
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