Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #27346

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

Improve sbws bandwidth accuracy

Better designs SHOULD:

  • use at least 4 measurements that are at least 6 hours apart, because:
    • there is a daily cycle
    • each day contains 2 similar points in the cycle (it is an up and down cycle)
    • if all 4 measurements happen within a few hours, they will still be biased
  • use at least 3 days of observed bandwidths, because:
    • a single download at the changeover point can affect 2 days
  • weight bandwidths based on the time since the last bandwidth, because:
    • if we only record bandwidths when they change, bandwidths that are updated soon after the last bandwidth are weighted too high
    • we can either:
      • record the bandwidths every hour, even if they haven't changed
      • weight each bandwidth by the time since the last bandwidth
  • use a decaying average for measured and observed bandwidths, because:
    • recent bandwidths are closer to the relay's current capacity
    • and we want accurate results
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking