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 133
    • Issues 133
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • 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
  • #4708

Closed
Open
Opened Dec 13, 2011 by Mike Perry@mikeperryOwner

Implement bwauth cap for latency

Robert, Sebastian and I hashed out an idea for another feedback mechanism for the bw auths based on latency.

Basically, the idea is to create another cap called latency_error similar to how we use circ_error. If a node's latency exceeds some quantile of the population (by being higher than the latencies of say 75% of all nodes), we would then compute and use a pid_error-style error value based on the distance from this 75% quantile setpoint, and use it if it is a more negative number than pid_error and circ_error.

I think the way we want to measure this latency is from CREATE to STREAM FAILED EXITPOLICY for a circuit creation + stream failure for a 1-hop stream exit attempt to localhost. This way we measure both cryptoworker queue latency as well as orconn, circuit, and stream latency.

I think the simplest way to build this is as a separate process from bwauthority.py that simply builds 1-hop circuits and attempts to exit to localhost from them. It would then output a separate, additional measurement file for the network that would be read in by aggregate.py, and used to compute latency_error.

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