Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #40040
Closed (moved) (moved)
Open
Created Jan 11, 2021 by juga@jugaMaintainer

Should the pid KeyValues be added to the Bandwidth File so that the bandwidth values are calculated exactly as Torflow?

The way sbws calculates the bandwidth values, is very similar to Torflow (https://sbws.readthedocs.io/en/latest/torflow_aggr.html) but not the same because the pid values are not calculated nor added to the Bandwidth File.

It can be seen how longclaw's curve is different in https://metrics.torproject.org/totalcw.html.

Even when we'll have sbws measuring approximately the same number of relays as Torflow (when the longclaw's curve is also similar to the rest of bwauths in https://consensus-health.torproject.org/graphs.html "bwauths"), the total bandwidth will still be a bit different.

Assignee
Assign to
Time tracking