Skip to content
GitLab
Projects Groups Snippets
  • /
  • 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
  • #33704
Closed (moved) (moved)
Open
Issue created Mar 24, 2020 by George Kadianakis@asn

Understand code performance of onion services under DoS

We need to do the following experiments to understand more about the performance of Tor under simulated DoS conditions:

  1. Get vanilla profile (for #30221 (moved)) [VANILLA profile] [Also get with INTRO2 rate limiting]

  2. See effect of DoS on intro and guard [VANILLA profile] [Also with INTRO2 rate limiting]

  3. Investigate control port experiment (with STREAM events enabled and trying to kill circs with CLOSECIRCUIT) [VANILLA profile] wrt ​https://lists.torproject.org/pipermail/tor-dev/2019-December/014097.html

    NEED: Controller script that logs circuit events and tries to kill some circuits [asn]

  4. Investigate size of replay cache (#26294 (moved)) [VANILLA profile] [asn]

  5. Investigate capacity of reestablish intro circuit (#26294 (moved)) [VANILLA profile]

  6. Compare intro/rend profiles (value of prop255 / #17254 (moved)) [VANILLA profile]

7~) Investigate horizontal scaling with OB (scale to 2/4/8 instances, extrapolate onwards.) [OBv3 profile]

8~) Investigate pinned paths with HSLayer2Node HSLayer3Node [Vanguard profile]

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