Opened 6 days ago

Last modified 6 days ago

#27107 new defect

Transition plan from Torflow to sbws

Reported by: juga Owned by:
Priority: Medium Milestone: sbws 1.0 (MVP must)
Component: Core Tor/sbws Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: #25925 Points:
Reviewer: Sponsor:

Description (last modified by juga)

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
    • 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
  3. i'd create child tickets for the WIP
    • implement torflow scaling
    • check sbws using torflow scaling compare to Torflow
    • change specification
    • ...
  4. Get one bwauth to run sbws
  5. Archive bw files (#21378)
  6. Compare Tor bw files from bwauths running Torflow and from the one running sbws
  7. ...

Edit:

  • formatting

Child Tickets

TicketStatusOwnerSummaryComponent
#27108acceptedjugaImplement torflow's scaling method in sbwsCore Tor/sbws

Change History (1)

comment:1 Changed 6 days ago by juga

Component: - Select a componentCore Tor/sbws
Description: modified (diff)
Note: See TracTickets for help on using tickets.