[tor-bugs] #16696 [- Select a component]: BWauth no-consensus fallback logic may need revision

[Tor Bug Tracker & Wiki]

#16696: BWauth no-consensus fallback logic may need revision
--------------------------------------+-----------------
     Reporter:  starlight             |      Owner:
         Type:  defect                |     Status:  new
     Priority:  major                 |  Milestone:
    Component:  - Select a component  |    Version:
   Resolution:                        |   Keywords:
Actual Points:                        |  Parent ID:
       Points:                        |
--------------------------------------+-----------------

Comment (by karsten):

 Replying to [comment:3 mikeperry]:
 > Can we extract the exact consensuses where the bw auths were down, and
 create an overlay on top of the torperf graphs for 50k, 1MB, and 5MB at
 https://metrics.torproject.org/torperf.html and
 https://metrics.torproject.org/torperf-failures.html?
 >
 > Karsten did this some years ago the last time the bw auths failed, and
 we found that performance worsened by 4-5X when the bw auths were down for
 any significant duration. I'm curious if that's still the case.
 Unfortunately, I think we're currently seeing a lot of on-off flapping
 though, and not significant periods where they remain consistently down.

 It wouldn't be difficult to find out when there were fewer than 3 votes
 containing Measured values.  The [https://collector.torproject.org/archive
 /relay-descriptors/votes/ tarballs] are all available on CollecTor.  Mike,
 others, do you still care about this, and if yes, what time frame do you
 have in mind for these data (past 3 months, all of 2015, more)?  aagbsn,
 if people care, would you want to pick this up, or should I do this?

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