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
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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
  • #8190

Closed (moved)
Open
Opened Feb 08, 2013 by Roger Dingledine@arma

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 #4682 (moved) as well.

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