Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #24935

Closed (moved)
(moved)
Open
Created Jan 18, 2018 by Nick Mathewson@nickm🍬

Add (local) statistics to check accuracy of predicted circuit mechanism

Tor clients build "preconstructed" circuits in anticipation of user requests, so that when the client request arrives, the circuit is ready for use, and Tor can handle the client request with less latency.

In recent work, we've started preconstructing circuits for onion service usage; and we've refactored that a bit for changing ideas of onion service paths (#23101 (moved)). We've also caused and fixed a difficult-to-notice bug here in #18859 (moved), that lingered around for quite a while.

That last bug suggests that we don't have enough analysis to determine whether this feature is working well. There are two possible errors we could be making:

  • We could be preconstrucing circuits that are never used, thereby wasting resources.
  • We could be failing to preconstruct circuits that we will obviously need, thereby causing needless latency.

We should add a mechanism for a client to keep track of how many preconstructed circuits it has made, and how many it has thrown away unused. Additionally, we should track the hit/miss rate of looking up a preconstructed circuit when we need one.

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