[metrics-bugs] #21272 [Metrics]: Onionperf deployment

Tor Bug Tracker & Wiki blackhole at torproject.org
Fri Mar 17 16:28:56 UTC 2017


#21272: Onionperf deployment
-------------------------+------------------------------
 Reporter:  hiro         |          Owner:  metrics-team
     Type:  enhancement  |         Status:  needs_review
 Priority:  Medium       |      Milestone:
Component:  Metrics      |        Version:
 Severity:  Normal       |     Resolution:
 Keywords:               |  Actual Points:
Parent ID:               |         Points:
 Reviewer:               |        Sponsor:
-------------------------+------------------------------
Changes (by robgjansen):

 * cc: rob.g.jansen@… (added)


Comment:

 Replying to [comment:42 karsten]:
 > I took another look at the data and compared it to Torperf data.  Please
 find the attached graph.  I have two remaining questions before adding the
 new data to CollecTor:
 >
 >  - It looks like op-nl is quite a bit faster than the other OnionPerf
 and Torperf instances.  One measurement only took 80 milliseconds from
 making the request until receiving the last byte.  Is this realistic?  Or
 does OnionPerf take any shortcuts that the other instances don't take?
 >

 Looking at the relays chosen for that path, is looks like the full path
 is:
 Netherlands(client)-->France(guard)-->Germany(middle)-->France(exit)-->Netherlands(server)

 This means the latency on each of those links is about 10 milliseconds.
 That seems feasible to me, given how close those countries are and that
 the machines are probably well connected to the backbone. The server can
 send all ~100 cells at once and it will likely travel through Tor in one
 piece, so I don't think that would cause any or much delay.

 Since most of the Tor relay bandwidth is in Europe, more of the circuits
 of a client in Europe would not leave the continent compared to clients in
 other regions. I'm not surprised if an OnionPerf client in Europe would
 trend faster than other countries on average. I wonder if either but not
 both of the two TorPerf nodes are in Europe, as we could potentially use
 the data they collect to test my hypothesis.

 Also, there is more information about that circuit in particular and the
 download process in general in the json.xz files that are also dumped to
 the data directory. I added some notes to the elements there quite some
 time ago to help us understand what is available:

 https://github.com/robgjansen/onionperf/blob/master/README_JSON.md

 Finally, I have been running my OnionPerf instance since April 2016, and
 would like to contribute to Tor metrics. Is that possible? I think it
 would be great if you could import the data that I have been collecting if
 it's valid (someone should double check that it's valid first, and I'm
 happy to do so). If there is something about my setup that you would
 prefer that I change before accepting data from my instance, please let me
 know. Also, if you want all instances to be run by TPI, let me know that
 too so I can stop paying for the VPS.

 http://onionperf.robgjansen.com:8081/

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21272#comment:43>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the metrics-bugs mailing list