#25687: over-report of observed / self-measure bandwidth on fast hardware -- important to torflow / peerflow --------------------------+---------------------------------- Reporter: starlight | Owner: (none) Type: defect | Status: new Priority: Medium | Milestone: Tor: unspecified Component: Core Tor/Tor | Version: Tor: 0.2.6.10 Severity: Normal | Resolution: Keywords: tor-bwauth | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: --------------------------+----------------------------------
Comment (by starlight): The concern of this ticket is with regard to the observed value published by the daemon rather than the Torflow calculated vote resulting from it. I suspect that changes to measurement logic in the daemon have likely reduced or eliminated the error last definitively observed in 2.6.10. I may yet write a monitor to evaluate the quality of daemon measurements. Torflow adjusts self-report with the ratio of the measured bandwidth for a relay to the average of all measured bandwidths in a manner short on nuance. Wrote about possible ways to address that here: https://github.com/torproject/sbws/issues/182#issuecomment-410745893 Have considered opening a Trac ticket encompassing the ideas, but am waiting for an opportune moment at a point where serious comparison work is evident. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25687#comment:10> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs