[tor-bugs] #2476 [Tor Client]: Run torperf on the sat link

[Tor Bug Tracker & Wiki]

#2476: Run torperf on the sat link
------------------------+---------------------------------------------------
 Reporter:  mikeperry   |       Owner:  ioerror
     Type:  task        |      Status:  new    
 Priority:  normal      |   Milestone:         
Component:  Tor Client  |     Version:         
 Keywords:              |      Points:         
   Parent:              |  
------------------------+---------------------------------------------------

Comment(by mikeperry):

 Replying to [comment:9 karsten]:
 > Changing a network-wide parameter to test the performance of a single
 Tor client seems like the wrong approach.  We won't get two tests for
 free, but we'll influence the results of the sat link measurements in a
 way we don't understand.  We'll always have time to play with consensus
 parameters and our standard torperfs at a later time.
 >
 > Is there a way to change the 'cbtquantile' parameter on the Tor client
 only?  If not, should we just patch it for the measurements?

 I totally disagree. The cbtquantile is a parameter that could very well
 have emergent effects. It's exactly the type of thing that you could set
 to a value like '20' on just one tor client and arrive at the conclusion
 that it works great. Testing a value out on the whole network in this
 situation is therefore actually like 3 tests for free even, not just 2. We
 get to see what sort of load that this induces on our servers *and* we get
 to see if the combination of more circuit creation and the lower value
 actually improves one or both of the sat link and the broadband link.

 Really the only reason not to do it yet is that we don't have *enough*
 clients yet running 0.2.2.x. But this isn't a valid reason not to try it
 either. It just means that we'll see less of an increased load on our
 nodes..

 > Also, keep in mind that 288 data points per day are not much to compare
 them to the standard torperfs, so running an unchanged torperf on the sat
 link for a couple of days might be useful.

 This is a different matter. Maybe we should just run the 50kb slightly
 more often? If we can't fetch 50kb in 3 min, isn't that pretty much a
 failure anyways? Circuits should be timing out on the order of 7-30
 seconds... Test #2477 should also give us data on this for the sat link,
 so we should certainly try this first and see what the minimum retry value
 is.

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