Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
S
sbws
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 131
    • Issues 131
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • 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.

  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #40028

Closed
Open
Created Dec 08, 2020 by juga @jugaMaintainer

Prioritize relays to be measured as torflow

sbws prioritize the relays to be measured only by the time they were latst measured. Initially it was also prioritizing the relays that failed to be measured, but we stop doing that since it looked those relays will fail again and delay other measurements (#28868 (closed)).

Torflow seems to order the relays obtained from the consensus by calculating a ratio dividing the maximum between the consensus bandwidth and the the minimum descriptor bandwidth (usually the observed bandwidth), when they relay is measured or the minimum of the descriptors bandwidth if the relay is unmeasured, and the minimum descriptor bandwidth (https://gitweb.torproject.org/pytorctl.git/tree/TorCtl.py#n1643).

So, for unmeasured relays, this ratio will be 1, higher for relays with higher consensus than descriptors bandwidth and lower for relays with lower consensus than descriptors bandwidth.

I'm not sure yet how this could affect the total number of relays being measured (#29710 (closed)).

Assignee
Assign to
sbws: 1.2.x-final
Milestone
sbws: 1.2.x-final
Assign milestone
Time tracking
None
Due date
None