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

Re: [tor-bugs] #7157 [Tor]: "Low circuit success rate %u/%u for guard %s=%s."

#7157: "Low circuit success rate %u/%u for guard %s=%s."
-----------------------------------------+----------------------------------
 Reporter:  arma                         |          Owner:                    
     Type:  enhancement                  |         Status:  needs_revision    
 Priority:  normal                       |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor                          |        Version:                    
 Keywords:  tor-client, MikePerry201211  |         Parent:                    
   Points:                               |   Actualpoints:  8                 
-----------------------------------------+----------------------------------
Changes (by mikeperry):

  * keywords:  tor-client, MikePerry201210 => tor-client, MikePerry201211
  * status:  needs_review => needs_revision


Comment:

 I created #7341 for the timeout issue. Any magical insight on the
 truncation problem? Should we just switch to double-precision floating
 point for the state file counts? Or maybe we should use a real (weighted?)
 moving average and simply store a count and a double rate value, and
 publish some kind of weight in the consensus?

 I am worried that the pattern Nick mentions is technically exploitable by
 guards to prevent scaling. I don't know if I should be more worried about
 that, or about the ability to ensure accuracy..

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