Opened 7 months ago

Last modified 7 months ago

#33704 new defect

Understand code performance of onion services under DoS

Reported by: asn Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-dos tor-hs network-team-roadmap-2020Q1
Cc: Actual Points:
Parent ID: #33703 Points:
Reviewer: Sponsor:

Description (last modified by asn)

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) [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 ​

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

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

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

6) Compare intro/rend profiles (value of prop255 / #17254) [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]

Child Tickets

Change History (3)

comment:1 Changed 7 months ago by asn

Description: modified (diff)

comment:2 Changed 7 months ago by asn

Description: modified (diff)

comment:3 Changed 7 months ago by asn

Hello, I have a branch that does the stuff for replay-cache xperiment (4) and also tries to improve diagnostics for intro-reestablish experiment (5):

I've sent email to mansoon for info on the control script required for control port experiment (3).

Last edited 7 months ago by asn (previous) (diff)
Note: See TracTickets for help on using tickets.