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

Closed (moved)
Open
Opened Mar 10, 2019 by juga @juga💬

Consider storing measured bandwidth for both the measured relay and the helper relay

Currently sbws store the measurement for the relay that was selected to be measured, but probably the measurement should also be stored for the helper relay, which would reduce to the half the measurements needed.

The main difference would be that the helper measurement would be with a relay that have the same or half bandwidth instead of with a relay that have double or same bandwidth, which might restrict its bandwidth.

To mitigate this, it could be checked whether it was a helper and then measure it next time as the node to measure.

Different to #28463 (moved), though related.

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#29720