[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #2476 [Tor Client]: Run torperf on the sat link
#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:7 mikeperry]:
> We should tweak the 'cbtquantile' consensus parameter a bit and see what
effect changing it has on our regular torperf runs *and* these. Tweaking
it in the consensus not only allows us to get two tests for free at the
same time, it also allows us to see what the network-wide effects are.
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?
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.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2476#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs