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
  • #2550
Closed (moved) (moved)
Open
Created Feb 14, 2011 by Roger Dingledine@armaOwner

bwauth should reschedule quicker bandwidth test when bandwidthrate changes?

https://metrics.torproject.org/relay-search.html?search=AEIOUm+2011-02-13

He apparently switches between 100KB/s and 2MB/s bandwidthrate depending on time of day. His bwauth votes ended up being very skewed:

moria1 says
w Bandwidth=141 Measured=15

ides says
w Bandwidth=141 Measured=26

urras says
w Bandwidth=141 Measured=1480

gabelmoo says
w Bandwidth=141 Measured=935

It's a shame that we're giving really low numbers to a node that wants to be 2MB/s at some times of day. It probably also means we give high numbers to a slow node if the measurement times are different.

Assignee
Assign to
Time tracking