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 121
    • Issues 121
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • 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.

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

Closed
Open
Opened Mar 14, 2019 by juga @juga💬Maintainer

Consider measuring all the network at once

Currently sbws has the "prioritization loop" and measures a subsets of relays. In legacy/trac#28547 (moved) we try to monitor all the relays that does not get measured. It would be probably way simpler to just measure all the relays currently in the network, which will tell us in one loop and around 30 hours whether not all relays were measured.

Assignee
Assign to
sbws: unspecified
Milestone
sbws: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/network-health/sbws#29783