Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #29720
Closed
Open
Created Mar 10, 2019 by juga@jugaMaintainer

Consider storing measured bandwidth for both the measured relay and the helper relay

Currently sbws store the measurement for the relay that was selected to be measured, but probably the measurement should also be stored for the helper relay, which would reduce to the half the measurements needed.

The main difference would be that the helper measurement would be with a relay that have the same or half bandwidth instead of with a relay that have double or same bandwidth, which might restrict its bandwidth.

To mitigate this, it could be checked whether it was a helper and then measure it next time as the node to measure.

Different to legacy/trac#28463 (moved), though related.

Assignee
Assign to
Time tracking