Opened 6 years ago

Closed 2 years ago

#9368 closed enhancement (wontfix)

Turn static throttling on in the live network

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-dirauth bandwidth analysis dos needs-analysis
Cc: karsten Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by arma)

The feature is all implemented, and it works as far as we know. Some static throttling of super-loud clients would help free up the network for the rest of the users.

There are three parts to this ticket:

A) Get the directory authorities to add the right consensus params. And also decide what numbers to use. I think "perconnbwrate=50000 perconnbwburst=10000000" (i.e. burst of 10MB and rate of 50KB/s) would do it.

B) Before it can go live, we need to do something about the bwauthorities -- they suck down 64MB files from the fastest relays, and step A will throttle them, leading to confused results. The simplest hack I've thought of is to make them relays, and then they don't get throttled. (#9369)

C) Some way to measure if it's going right (general performance improves) or wrong (it's harming normal users). Ordinarily I'd be a big fan of getting all this infrastructure set up and doing an experiment, but that's going to take a year or more at this rate, and we could make a difference right now.

Child Tickets

TicketTypeStatusOwnerSummary
#9369enhancementclosedaagbsnMove the bwauths to be relays, so they won't get throttled
#9762enhancementclosedaagbsnMake a torflow option that starts every testing circuit at a local Tor relay first

Change History (9)

comment:1 Changed 6 years ago by arma

Description: modified (diff)

comment:2 Changed 6 years ago by arma

Oh, and there's D) What else is this going to break?

comment:3 Changed 6 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:4 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:5 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:6 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:7 Changed 2 years ago by dgoulet

Keywords: tor-dirauth added; tor-auth removed

Turns out that tor-auth is for directory authority so make it clearer with tor-dirauth

comment:8 Changed 2 years ago by nickm

Keywords: bandwidth analysis dos needs-analysis added
Severity: Normal

comment:9 Changed 2 years ago by teor

Resolution: wontfix
Status: newclosed

We never turned on perconnbwrate in the consensus, so these tickets are "wontfix".

Note: See TracTickets for help on using tickets.