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
  • #30417

Closed (moved)
(moved)
Open
Created May 06, 2019 by cypherpunks@cypherpunks

Quicken CBT latency on updated/restarted nodes

With probability of choosing path selection from consensus, we could guess and build preemptively inter-relay connections.

If we cannot simple preconnect orcon to any node. May something like this could still benefit in lower latency after bootstrapping. for very uptodate nodes and nonstable.

Exit: build preemptively inter-relay connections to middle (non guard flag, non exit flag) but low probability of connection coming from guard directly (guard have low middle probability)
Guard: build preemptively inter-relay connections to suspected middle relays Middle: build preemptively inter-relay connections to approximately anything?

The idea is of having benefits from the way of clients do build circuits preemptively. Guess it, build it and leave it open in idle state for future use without building on the fly without TCP/tls rtt.

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