#27107: Transition plan from Torflow to sbws --------------------------------------+--------------------------------- Reporter: juga | Owner: (none) Type: defect | Status: new Priority: Medium | Milestone: sbws 1.0 (MVP must) Component: - Select a component | Version: Severity: Normal | Keywords: Actual Points: | Parent ID: #25925 Points: | Reviewer: Sponsor: | --------------------------------------+--------------------------------- Ticket for the tasks related to get sbws in production. These would include work we have been already doing, but probably we should need to add more tasks:
1. Get sbws in Debian (#26848) 2. Check that the bandwidth files results are similar to Torflow: We have being doing this in https://github.com/pastly/simple-bw- scanner/issues/182, though is growing. So far we checked: - sbws raw results compared to torflow: shape is quite different Measured from the same box in different days: - sbws raw results compared to sbws scaled: big relays get bigger bw, but shape still different from torflow - sbws raw results compared to sbws raw results having a bigger time for downloading: they're similar - sbws raw results compared to sbws raw results resting the rtt from the dowload time: they're similar - implement parsing Torflow raw files - sbws raw results compared to Torflow results: they are similar, so it is the scaling method which makes results different 2.1 i'd create child tickets for the WIP - implement torflow scaling - check sbws using torflow scaling compare to Torflow - change specification - ... 3. Get one bwauth to run sbws 4. Archive bw files (#21378) 5. Compare Tor bw files from bwauths running Torflow and from the one running sbws 6. ... -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27107> 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