Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
O
Onionperf
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • 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
  • Metrics
  • Onionperf
  • Issues
  • #33399

Closed
Open
Opened Feb 20, 2020 by Ana Custura@acuteDeveloper

Measure static guard nodes with OnionPerf

The specifications for measuring this are as follows:

  • OP should measure one guard or set of guards at a time. It could use NumEntryGuards in the torrc file to support more than 1 guard
  • A new guard/set of guards must be chosen after a day of measurement
  • All CBT data must be erased when choosing a new set of guards, after day of measurements (at UTC midnight). This could mean erasing or replacing the state file for CBT.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
OnionPerf: Scalability, Performance, Establishing Basline Metrics
Milestone
OnionPerf: Scalability, Performance, Establishing Basline Metrics (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/metrics/onionperf#33399