Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T torflow
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • torflow
  • Issues
  • #3444
Closed
Open
Issue created Jun 21, 2011 by Mike Perry@mikeperryOwner

Bw auths should group nodes by ratio (stream capacity), not consensus bw

Right now, the bw auths group nodes into "slices" of 50 nodes of similar consensus bandwidth. This is probably not the optimal grouping. They should instead be grouped by stream capacity. This is also equivalent to grouping them by the ratio of the consensus bandwidth to the descriptor bandwidth.

This would be implemented as a PathSupport.RatioPercentRestriction. We should then be able to easily switch from PercentileRestrictions to RatioPercentileRestrictions without too much issue.

This will result in faster scans and more accurate measurements.

Assignee
Assign to
Time tracking