Opened 8 years ago

Closed 5 years ago

#4903 closed task (fixed)

consider turning ewma circ priority back on

Reported by: arma Owned by:
Priority: Medium Milestone:
Component: Metrics/Analysis Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


When we switched to consensus method 12, we lost the threshold of votes required to set CircuitPriorityHalflifeMsec in the consensus. So EWMA has been off.

Is this actually bad? Recent preliminary results from Shadow and ExperimenTor show that the ewma circ priority feature is actually not helpful.

In any case, we should make an explicit decision rather than just getting dumped into the current situation.

Child Tickets

Change History (6)

comment:1 Changed 8 years ago by arma

Ok, we turned it back on accidentally when Sebastian told everybody to set it in their consensus params today.

I wonder if there will be any evidence in the torperf output of the latest change.

comment:2 in reply to:  1 Changed 8 years ago by arma

Resolution: wontfix
Status: newclosed

Replying to arma:

I wonder if there will be any evidence in the torperf output of the latest change.

In retrospect, the change from the bwauth behavior will probably swamp any change we might see from the circuit priority change. Oh well.

I'm going to close this ticket.

comment:3 Changed 8 years ago by Sebastian

Resolution: wontfix
Status: closedreopened

According to what Mike said bwauth behaviour should not actually have changed at all

comment:4 Changed 7 years ago by arma

Ok to close ticket again?

comment:5 Changed 7 years ago by arma

(For posterity, our current thinking via Rob is that circuit-level EWMA isn't showing any real improvements, in large part because we're picking connections round-robin, and after we've chosen a connection we're picking the most suitable circuit. That means we often are not choosing the most suitable global circuit. See also #4585.)

comment:6 Changed 5 years ago by arma

Resolution: fixed
Status: reopenedclosed

Closing, since ewma is indeed back on (though we still think it's the case that it's mostly useless, until we get a global circuit scheduler in place, and maybe more pieces of KIST too).

Note: See TracTickets for help on using tickets.