Opened 9 years ago

Last modified 16 months ago

#4708 new enhancement

Implement bwauth cap for latency

Reported by: mikeperry Owned by:
Priority: Medium Milestone: sbws: unspecified
Component: Core Tor/sbws Version:
Severity: Normal Keywords: performance
Cc: rransom, arma, Sebastian, aagbsn Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Robert, Sebastian and I hashed out an idea for another feedback mechanism for the bw auths based on latency.

Basically, the idea is to create another cap called latency_error similar to how we use circ_error. If a node's latency exceeds some quantile of the population (by being higher than the latencies of say 75% of all nodes), we would then compute and use a pid_error-style error value based on the distance from this 75% quantile setpoint, and use it if it is a more negative number than pid_error and circ_error.

I think the way we want to measure this latency is from CREATE to STREAM FAILED EXITPOLICY for a circuit creation + stream failure for a 1-hop stream exit attempt to localhost. This way we measure both cryptoworker queue latency as well as orconn, circuit, and stream latency.

I think the simplest way to build this is as a separate process from that simply builds 1-hop circuits and attempts to exit to localhost from them. It would then output a separate, additional measurement file for the network that would be read in by, and used to compute latency_error.

Child Tickets

Change History (6)

comment:1 Changed 8 years ago by mikeperry

Owner: changed from mikeperry to aagbsn
Priority: normalmajor
Status: newassigned

comment:2 Changed 3 years ago by teor

Parent ID: #13630
Severity: Normal

This is a feature that belongs in the new bwauth replacement project, see #13630.

comment:3 Changed 3 years ago by teor

Priority: HighMedium

Priorities and Severities in torflow are meaningless, setting them all to Medium/Normal.

comment:4 Changed 3 years ago by teor

Owner: aagbsn deleted

aagbsn was the default owner, unassigning

comment:5 Changed 3 years ago by teor

Status: assignednew

Mark all tickets that are assigned to nobody as "new".

comment:6 Changed 16 months ago by teor

Component: Core Tor/TorflowCore Tor/sbws
Milestone: sbws: unspecified
Parent ID: #13630

If we do this, it will be in sbws

Note: See TracTickets for help on using tickets.