Opened 9 years ago

Closed 9 years ago

#2545 closed defect (fixed)

Verify that #1919 Torperfs are working correctly

Reported by: karsten Owned by: mikeperry
Priority: Medium Milestone:
Component: Metrics/CollecTor Version:
Severity: Keywords:
Cc: Actual Points: 2
Parent ID: Points: 2
Reviewer: Sponsor:


The results of the #1919 Torperfs so far don't indicate a big difference of Tor clients picking the slowest or fastest guards. We should verify that the script is working correctly. I uploaded the entrycons_logs files of all 12 Torperf runs here (47M) for further analysis.

Child Tickets

Change History (2)

comment:1 Changed 9 years ago by mikeperry

We should also correlate the choices of with what actually happened according to the control port's circuit history in the path data at:

comment:2 Changed 9 years ago by mikeperry

Actual Points: 2
actualpointsdone: 2
Points: 2
pointsdone: 2
Resolution: fixed
Status: newclosed

Turns out that there is a bug here. I've written the verification script and it showed us that guard nodes were not being selected properly. We tracked it down to the fact that the controlled torperfs were still setting UseEntryGuards 0. I will commit a fix to this in another bug.

Note: See TracTickets for help on using tickets.