[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #20534 [Core Tor/Tor]: Revise hard-coded download schedules
#20534: Revise hard-coded download schedules
--------------------------+------------------------------------
Reporter: teor | Owner:
Type: defect | Status: needs_information
Priority: Medium | Milestone: Tor: 0.2.9.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: regression | Actual Points:
Parent ID: #20499 | Points: 0.5
Reviewer: | Sponsor:
--------------------------+------------------------------------
Comment (by teor):
Replying to [comment:4 dgoulet]:
> Replying to [comment:3 teor]:
> > Actually, there's not much point in revising these schedules - the
exponential backoff code only pays attention to the first and last value
in the schedule.
>
> teor, should we keep this in 029 then? Or the ticket at all?
If we revert the exponential backoff code as our solution to #20499, we
will want to tweak the final times on some of these schedules, to achieve
Roger's goal of "never have a relay stop trying entirely".
If we don't, we will want to adjust the initial time as well.
So I think my comment was a bit hasty - it's only the middle times that
don't matter, and only if we keep exponential backoff.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20534#comment:5>
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