[tor-bugs] #1944 [Torperf]: Set up a Torperf to a hidden service

[Tor Bug Tracker & Wiki]

#1944: Set up a Torperf to a hidden service
-------------------------+----------------------
     Reporter:  arma     |      Owner:
         Type:  task     |     Status:  assigned
     Priority:  normal   |  Milestone:
    Component:  Torperf  |    Version:
   Resolution:           |   Keywords:  SponsorR
Actual Points:           |  Parent ID:  #2552
       Points:  3        |
-------------------------+----------------------

Comment (by karsten):

 How about we stop the current set of measurements, archive the results,
 tweak the scripts to analyze them and make plans for making future results
 more useful, and then start another round of measurements?  Unless there's
 a benefit in collecting more data in the current setup?

 Want to make the analysis script better for finer granularity?  Note that
 I left out events coming from the introduction circuit on purpose: we'd
 have to match rendezvous circuit and introduction circuit somehow, and
 there's no single unique identifier that we could use for that.  But
 please see the Python script in my Markdown file for details.

 Speaking of unique request identifiers and hidden-service-side
 measurements: do you think we could link events using hidden service
 subdomains?  I was thinking randomnumber.ourservice.onion or
 timestamp.ourservice.onion.  Or maybe there's a better way?

 And yes, in the future we can set up a single Torperf instance that
 requests 50 KiB files.  Well, in theory, we could do 1 KiB files if we
 really, really only care about connection establishment.  What do you
 think?

 I fixed the graphs on the server by zooming into range [0, 300].

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