Opened 10 years ago

Closed 10 years ago

#1918 closed enhancement (implemented)

annotate torperf output with paths

Reported by: arma Owned by: Sebastian
Priority: Medium Milestone: Deliverable-Sep2010
Component: Metrics/CollecTor Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: #1766 Points:
Reviewer: Sponsor:


Torperf's results right now represent the average performance that users should expect to see. But part of the problem with the Tor network right now is that the variance is high. One component contributing to this variance is the fact that different users choose different entry guards. It seems clear that Tor network performance is a function of (among other things) the entry guards you've picked.

There's lots of analysis we should do to try to learn more about what performance you should expect from having which guards. A prerequisite for all of this analysis is knowing which first hop is used in each torperf run.

So we should modify torperf to annotate in its logs what path was chosen for that request. (For now, we only really want the first hop; but I bet we'll find a good use for knowing the other hops too.)

Child Tickets

Change History (6)

comment:1 Changed 10 years ago by Sebastian

Owner: changed from karsten to Sebastian
Status: newassigned

Looks like a very useful thing. This would also allow us to calculate entropy of path selection etc for the real network with all the availability etc constraints. Maybe we should run at least two instances of torperf just for that.

comment:2 Changed 10 years ago by Sebastian

Do we need more information than timestamp and the three hops?

comment:3 Changed 10 years ago by Sebastian

Example implementation is running on my torperf instances for the perconnbwrate experiment.

Data available at|1mb|5mb).extradata

comment:4 Changed 10 years ago by asn


comment:5 in reply to:  4 Changed 10 years ago by rransom

Replying to asn:


Please subscribe to tor-bugs.

comment:6 Changed 10 years ago by Sebastian

Resolution: implemented
Status: assignedclosed

Closing this as implemented since we currently have more than 15 torperf instances running with this code and it appears to work quite well. We might want to add some more analysis stuff later on.

Note: See TracTickets for help on using tickets.