[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #34024 [Metrics/Onionperf]: Reduce timeout and stallout values
#34024: Reduce timeout and stallout values
---------------------------------------+--------------------------------
Reporter: karsten | Owner: metrics-team
Type: enhancement | Status: needs_review
Priority: Medium | Milestone:
Component: Metrics/Onionperf | Version:
Severity: Normal | Resolution:
Keywords: metrics-team-roadmap-2020 | Actual Points:
Parent ID: | Points: 1
Reviewer: | Sponsor: Sponsor59-must
---------------------------------------+--------------------------------
Changes (by karsten):
* status: new => needs_review
Comment:
I looked at measurements made by op-hk2, op-nl2, and op-us2 in the first
half of May 2020. I wanted to get an idea how many of the 5 MiB
measurements would have timed out with a timeout of 270 rather than 3600
seconds. The result was: ''zero''. For comparison, there have been 1,027
successful 5 MiB measurements in that time, and the slowest four have
finished in 201 seconds, 186 seconds, 142 seconds, and 128 seconds. And
while it's conceivable that we would find a non-zero number in other half
months of measurements, their number will very likely be really small.
Similar to #34023, let's discuss how to proceed here. My recommendation is
that we:
1. use a timeout of 270 seconds for all measurements to avoid overlapping
measurements and
2. set the stallout value to 0 to disable the stallout function in TGen.
More on Thursday at the weekly meeting.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/34024#comment:6>
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