Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
S
sbws
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 131
    • Issues 131
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #27107

Closed
Open
Created Aug 12, 2018 by juga @jugaMaintainer

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:

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

Edit:

  • formatting
Assignee
Assign to
sbws: unspecified
Milestone
sbws: unspecified
Assign milestone
Time tracking
None
Due date
None