[tor-scaling] Tuning KIST and EWMA parameters

[Mike Perry]

Rob Jansen:>> On Jun 7, 2019, at 8:18 AM, David Goulet
<dgoulet at torproject.org> wrote:
>>
>> So it appears that we might want to do a tor release with KISTSchedRunInterval
>> being different values for client and relays? Or just tell the world to use
>> "2msec" for their onion service but that won't work well...
> 
> Please, please, please let's first fix the off-by-one bug so that "KISTSchedRunInterval 2 msec" does not really mean "KISTSchedRunInterval 1 msec"..
See LTS discussion: the fix you are requesting means that we can't
update the consensus parameter in a controlled way until February 2022
(see also
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases).

So, to keep things expedient, please please please please please try to
find ways not to require such delay. Don't panic! We are tuning features
that have supposedly been subject to sufficient experimental rigor already.

Good point of order, also: for performance tuning, anything that
requires relay patching is out. That stuff belongs in the "Develop"
column of the kanban (and I can add it there, but not for cases like this).

> and so "KISTSchedRunInterval 1 msec" doesn't cause an infinite loop (or whatever the buggy behavior is).

"Doctor, it hurts when I--"

"Don't do that, then."

"Doctor, I don't know what might hurt!"

"Try to guess; otherwise, stop when it hurts."

-- 
Mike Perry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-scaling/attachments/20190609/c2011f13/attachment-0001.sig>