Torperf
Sebastian Hahn
mail at sebastianhahn.net
Sun Oct 17 10:19:06 UTC 2010
On Oct 15, 2010, at 4:13 AM, Mike Perry wrote:
> I would love to have all of these datastream available for comparison
> when various events and perf tweaks change the network. In fact, I
> would love it if we could have the following 5 torperf runs logging
> continuously and all overlayed on the main Torperf metrics graph:
>
> 1. Fastest 3 guards by network status
> 2. Fastest 3 guards by ratio of ns_bw/desc_bw
> 3. EntryGuards=0 (default current torperf)
> 4. Slowest 3 guards by network status
> 5. Slowest 3 guards by ratio of ns_bw/desc_bw
>
> Is it hard to keep all of these running and logging for some reason?
> Does the 1919 script take up a lot of RAM?
The problem wasn't that the script was taking a lot of RAM, but rather
that each torperf instance comes with its own tor instance. Spinning
up another 9 clients caused the memory issues.
> I can make these and any other changes to the 1919 script to help this
> along.
So far it appears the script is doing fine.
Sebastian
More information about the tor-dev
mailing list