Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • 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.

  • Legacy
  • TracTrac
  • Issues
  • #21992

Closed (moved)
Open
Opened Apr 19, 2017 by teor@teor

Consensus Health: how many medians does each bandwidth authority control?

When we change the bandwidth authorities, we want to know what impact this has on their measurements.

This matters most for:

  • new bandwidth authorities, and
  • changing the location of bandwidth authorities or bandwidth servers

It would help us if we knew for each relay:

  • the median bandwidth authority: the bandwidth authority that made the relay's median measurement

This tells us which authority has control over the measurement. One way to implement this would be to make the median bold in each relay's bandwidth row.

It would also help us if we knew for each bandwidth authority:

  • how many relays have its measurement as the median

One way to implement this is to add to the "Bandwidth scanner status" table: https://consensus-health.torproject.org/#bwauthstatus

longclaw 7845 measured 1569 median
gabelmoo 7419 measured 1484 median

It would also be helpful to have a graph of how this changes over time.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#21992