Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 313
    • Issues 313
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #8190
Closed
Open
Created Feb 08, 2013 by Roger Dingledine@armaReporter

Relays should publish number of refill intervals where the token bucket went dry

Our extrainfo descriptors have 15-minute intervals where we list the sum of bytes handled in that interval.

Intuitively, it seems that congestion should have to do with how many times we run out of tokens in our token bucket.

We could track the number of refills where our global buckets run dry, and publish the number of such refills in each 15-minute interval.

We probably want to track read bucket and write bucket separately; differences between the two might teach us something about legacy/trac#4682 (moved) as well.

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