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

Closed
Open
Opened Apr 11, 2013 by Damian Johnson@atagar

Issue with RelayBandwidthBurst handling

Miłosz reports...

I think I've spotted a mistake in arm. It would seem that the RelayBandwidthBurst setting from torrc is interpreted as a rate (so a setting of 2MB is shown as 16Mbit/s, for example), but, as I've recently learned, that is not what the setting actually defines.

What it does define is something along the lines of a "credit limit" - the bandwidth bucket grows with RelayBandwidthRate until it hits RelayBandwidthBurst. It is the maximum amount of data that can be transferred in a single "burst", rather than the maximum bandwidth. For a less incompetent explanation than my own, see https://trac.torproject.org/projects/tor/ticket/3630#comment:14

This seems to be a common misconception within the tor community (even to the point where some comments in tor's source code indicate it!).
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#8687