Transition plan from Torflow to sbws
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:
- Get sbws in Debian (#26848 (moved))
- 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
- 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
- i'd create child tickets for the WIP
- implement torflow scaling
- check sbws using torflow scaling compare to Torflow
- change specification
- ...
- Get one bwauth to run sbws
- Archive bw files (#21378 (moved))
- Compare Tor bw files from bwauths running Torflow and from the one running sbws
- ...
Edit:
- formatting
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information