Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 316
    • Issues 316
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #40160
Closed
Open
Created Oct 08, 2020 by Mike Perry@mikeperryDeveloper

Filter out relays according to candidate new Fast and Guard cutoffs

Once we have onionperf results with CBT and guards, we should create a stem script that emits a list of fingerprints for relays with bandwidth below candidate thresholds for Fast and Guard thresholds.

With this fingerprint list, we can use https://gitlab.torproject.org/tpo/metrics/onionperf/-/issues/33260 to filter out any onionperf circuits that contain fingerprints that would no longer be Fast. Same for Guard.

This analysis will help us learn if we need to change the Fast and Guard flag cutoffs to get improved performance from the network.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking