[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #33871 [Core Tor/sbws]: Scale exactly as torflow does?
#33871: Scale exactly as torflow does?
-------------------------------------------------+-------------------------
Reporter: juga | Owner: (none)
Type: defect | Status: new
Priority: Medium | Milestone: sbws:
| 1.1.x-final
Component: Core Tor/sbws | Version:
Severity: Normal | Resolution:
Keywords: sbws-majority-blocker, sbws-roadmap | Actual Points:
Parent ID: #33775 | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by juga):
Replying to [comment:2 teor]:
> There's a related bug here, that might only show up when the last
Torflow instance leaves the network.
>
> The target download time is 6 seconds. Tor's download measurement time
is 10 seconds. So on average, sbws will only be using 6/10 of a relay's
capacity over any 10 second period.
>
> I suggest that we make the average sbws download time at least 10
seconds, to avoid this issue.
Which is similar to ticket #28545 (with 11 seconds).
If understood correctly the way that Torflow calculates the new consensus
banwdwidth [0] (and might be worth someone double check), the measured
bandwidth influences very "little" on the new bandwidth (which i've try to
say some times).
So i think, that changing the download time have less impact on the new
calculated bandwidth than the consensus/descriptor previous bandwidth
values.
[0] https://onbasca.readthedocs.io/en/latest/torflow_aggr.html,
https://gitweb.torproject.org/torspec.git/tree/bandwidth-file-
spec.txt#n1167
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33871#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