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

[Tor Bug Tracker & Wiki]

#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:
-------------------------+------------------------------

Comment (by 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?

 {{{
 @type torperf 1.0
 BUILDTIMES=0.0799999237061,0.0899999141693,0.109999895096 CIRC_ID=5284
 CONNECT=1489499550.79 DATACOMPLETE=1489499550.87 DATAPERC0=1489499550.86
 DATAPERC10=1489499550.86 DATAPERC100=1489499550.87
 DATAPERC20=1489499550.86 DATAPERC30=1489499550.86 DATAPERC40=1489499550.86
 DATAPERC50=1489499550.87 DATAPERC60=1489499550.87 DATAPERC70=1489499550.87
 DATAPERC80=1489499550.87 DATAPERC90=1489499550.87
 DATAREQUEST=1489499550.82 DATARESPONSE=1489499550.84 DIDTIMEOUT=0
 ENDPOINTLOCAL=localhost:127.0.0.1:60802
 ENDPOINTPROXY=localhost:127.0.0.1:29128
 ENDPOINTREMOTE=37.218.247.40:37.218.247.40:8080 FILESIZE=51200
 HOSTNAMELOCAL=op-nl HOSTNAMEREMOTE=op-nl LAUNCH=1489499310.22
 NEGOTIATE=1489499550.79
 PATH=$A1EF24A8E85E440F215A5C296790636C62F43A2A,$150F2AD7D0FE7715ECAA642D4CD4BCBF95E8BD0D,$5CECC5C30ACC4B3DE462792323967087CC53D947
 QUANTILE=0.8 READBYTES=51269 REQUEST=1489499550.80 RESPONSE=1489499550.82
 SOCKET=1489499550.79 SOURCE=op-nl START=1489499550.79 TIMEOUT=1500
 USED_AT=1489499550.87 USED_BY=10787 WRITEBYTES=54
 }}}

  - The IP address of op-hk gets resolved to the Netherlands, though the
 measurements look very different from the op-nl host.  Can we confirm that
 the host is really located in Hong Kong and that it's just the IP-to-
 country resolution that is behind?

 If we have answers to these questions, I'd say let's make the data
 available.

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