[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #20922 [Core Tor/Tor]: Consider faster retry schedule for primary guards
#20922: Consider faster retry schedule for primary guards
--------------------------+------------------------------------
Reporter: nickm | Owner:
Type: defect | Status: needs_review
Priority: Medium | Milestone: Tor: 0.3.0.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: #19877 | Points:
Reviewer: | Sponsor:
--------------------------+------------------------------------
Comment (by asn):
I think this is a good change for the cases where we marked our primaries
as down while we were offline, and now we are only dealing with confirmed
guards. This change will make us go back to our primaries much faster.
That said, this change has performance implications when the top primary
guards are legitimately down, since we will have to wait about 2 minutes
for each primary guard connection to timeout every 10 minutes.
I currently think that this change is worth doing, but I would need to
test this branch more in real life situations to see if the performance
penalty is too annoying.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20922#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