[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

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

#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 starlight):

 Per Arma, no problems this time (after 2.5+ days):

 https://lists.torproject.org/pipermail/tor-relays/2015-August/007537.html

 I opine in the same thread that Tor runs better this way
 with the current relay environment.  Probably the result
 of the dropping cost and increasing availability of
 network capacity, improvements in the relay code, and
 shorting-out known issues with BWauths.  Appears that
 fewer than 50 high-capacity relays have lost consensus
 weight with the rest taking it up easily.

 An unscientific sample of six out of 234 previously
 Unmeasured=1 exit relays shows them now properly
 utilized.  Additional 250 non-exits are back in
 the game as well.

 https://lists.torproject.org/pipermail/tor-relays/2015-August/007539.html

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