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

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

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

How long should sbws keep measured and observed bandwidths?

In #27135 (moved), sbws starts keeping observed bandwidths for relays:

Taking the descriptor observed bandwidth only when the relay is measured and calculating the mean when there're several observed bandwidth values for the same relay

Here are some options:

  • use the latest measured and observed bandwidth
  • take the latest measured and observed bandwidth every hour, and
    • average the last N days of bandwidths
    • apply an exponentially decaying average to all bandwidths

We need to decide which strategy to use, update the bandwidth file spec, and implement this feature in sbws.

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