[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 karsten):

 Replying to [comment:10 mikeperry]:
 > Testing a value out on the whole network in this situation is therefore
 actually like 3 tests for free even, not just 2.

 OK, I don't know enough about 'cbtquantile' to make a solid statement
 here.  My comment was more a general one about changing more than one
 variable at once (here: ctbquantiles on an unknown number of Tor clients,
 not just on the one we're measuring).

 >> 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.

 Our only data comes from torperfs running on excellent network
 connections.  Hard to say if 3 minutes are a useful timeout for a sat
 link.

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