On 1/24/13 10:31 AM, Fabio Pietrosanti (naif) wrote:
On 1/21/13 9:06 PM, Karsten Loesing wrote:
Hi everyone,
you probably heard of Torperf [0], the tool that produces our Tor client performance graphs [1]. Torperf is mostly a bunch of scripts and lengthy HOWTOs, so setting it up and keeping it happy is not exactly trivial.
I am wondering if this should not use and leverage the existing OONI project that does "more or less" what functionally TorPerf has to do?
Which of Torperf's planned functionality overlaps with OONI?
- set up local Tor clients, configure them, and register for events;
- run a local web server to download files from or upload files to;
- periodically run one or more tests which can be:
3.1) an HTTP GET request over Tor to its own web server, 3.2) an HTTP POST request to measure upload speed, 3.3) a GET or POST request to a locally running hidden service, 3.4) a series of fetches of top 50 Alexa domains using Selenium/Firefox; 3.5) a series of requests to track stream/circ allocations for #5830; 4) store request timestamps and Tor controller events to SQLite; 5) provide results via a RESTful API over its web server.
For the moment, I think we're better off keeping the two projects separate, mostly because of Torperf's February 28 deadline. But I wouldn't mind integrating Torperf's functionality into OONI afterwards.
Arturo, maybe you can comment on this?
For everyone else following this thread, I updated the README to list next steps and incorporate all feedback I got so far:
https://gitweb.torproject.org/karsten/torperf.git/blob/perfd:/README.perfd
Best, Karsten