[tor-bugs] #2565 [Torperf]: Redesign Python parts in Torperf
Tor Bug Tracker & Wiki
torproject-admin at torproject.org
Fri Apr 29 08:17:05 UTC 2011
#2565: Redesign Python parts in Torperf
-------------------------+--------------------------------------------------
Reporter: karsten | Owner:
Type: enhancement | Status: assigned
Priority: minor | Milestone:
Component: Torperf | Version:
Keywords: | Parent:
Points: 8 | Actualpoints:
-------------------------+--------------------------------------------------
Comment(by karsten):
Here's my vague idea of how a redesigned Torperf could look like.
We'd have a single config file that contains all settings that we
currently write to the crontab and to the start script. A sample config
file might look like this:
{{{
TorperfGeneral
DataDirectory=/home/torperf/torperf/
TorBinary=/home/torperf/tor/src/or/tor
SourceString=ferrinii
StartSocksPorts=9020
StartControlPorts=10020
HttpServer=torperf.torproject.org
TorperfRun
Start=*/5
FileSize=50*1024
Timeout=295
TorperfRun
TorBinary=/home/torperf/tor-75/src/or/tor
Start=2,7,12,17,22,27,32,37,42,47,52,57
FileSize=50*1024
Timeout=295
Guards=slowratio
Cbt=75
}}}
We'd also have shell scripts to start and stop all Torperf runs described
in the config file. The only required change to the crontab would be to
add a @reboot line containing the start script.
Torperf would:
- create any missing Tor data directories and torrc's,
- start tors,
- connect to all the control ports to obtain path information and
possibly influence guard node selection,
- regularly call trivsocks-client to make requests,
- timeout runs that take too long, and
- write everything to a single output file, possibly in the format
described in #3036.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2565#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list