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

Closed (moved)
Open
Opened Aug 28, 2018 by teor@teor

Make the sbws node cap a proportion of the capped bandwidth

Here's a simple algorithm for capping relay bandwidths:

  1. Calculate the cap as X% of the total relay bandwidth before the cap
  2. If any relay is above the cap, set its bandwidth to the cap

But this algorithm calculates the cap as a proportion of the uncapped bandwidth, not the capped bandwidth. So the capped relays are actually slightly greater than X% of the capped bandwidth.

Maybe we will want to fix this issue eventually, but for the first release, the difference between X% and (X+1)% is not that important.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
sbws: 1.2.x-final
Milestone
sbws: 1.2.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#27363