Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #2526

Closed (moved)
(moved)
Open
Created Feb 10, 2011 by Mike Perry@mikeperry

Improve bandwidth test on Tor Weather

Tor Weather currently uses descriptor bandwidth to inform operators if their nodes are not providing sufficient capacity for various things. This may be useful for some tests, to simply tell relays if their relay stops transmitting any data, but it probably shouldn't be the only thing we check.

Using the "Bandwidth=" values from the NetworkStatus documents will allow us to also determine if a relay appears drastically underloaded, or overloaded as compared to it's peers. The best way to do this test is probably to take the "Bandwidth=" value and divide it by the descriptor bandwidth value. If this resulting number is 1.0 or larger, the relay is doing as well as or better than other relays. If this value is very low (0 is obviously lowest), then the relay is having trouble transitting data, and is that much slower on average than others.

So this is probably best classified as an enhancement, not a defect.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking