[or-cvs] r19704: {torperf} Reduce MaxCircuitDirtiness to 1 minute to avoid reusing the (torperf/trunk)

[kloesing@xxxxxxxx]

Author: kloesing
Date: 2009-06-10 15:56:40 -0400 (Wed, 10 Jun 2009)
New Revision: 19704

Modified:
   torperf/trunk/measurements-HOWTO
Log:
Reduce MaxCircuitDirtiness to 1 minute to avoid reusing the same circuit in edge cases.


Modified: torperf/trunk/measurements-HOWTO
===================================================================
--- torperf/trunk/measurements-HOWTO	2009-06-10 19:16:49 UTC (rev 19703)
+++ torperf/trunk/measurements-HOWTO	2009-06-10 19:56:40 UTC (rev 19704)
@@ -2,7 +2,7 @@
 ==================================================
 
 The performance (latency and throughput) that Tor users experience depends
-on numerous factors and is subject of current research. In order to
+on numerous factors and is the subject of current research. In order to
 evaluate progress in improving Tor's performance, we need to continuously
 measure how fast Tor really is for our users. The primary purpose of these
 measurements is to compare how performance evolves over time. This howto
@@ -12,7 +12,7 @@
 The following configuration parameters are used:
 
 - 50 KB file, downloaded every 5 minutes, timeout of 4:55 minutes,
-  MaxCircuitDirtiness of 4 minutes, SOCKS port 9020, no entry guards
+  MaxCircuitDirtiness of 1 minute, SOCKS port 9020, no entry guards
 - 1 MB file, downloaded every 30 minutes, timeout of 29:55 minutes, default
   MaxCircuitDirtiness of 10 minutes, SOCKS port 9021, no entry guards
 - 5 MB file, downloaded every 60 minutes, timeout of 59:55 minutes, default
@@ -45,7 +45,7 @@
 
 DataDirectory .
 SocksPort 9020
-MaxCircuitDirtiness 4 minutes
+MaxCircuitDirtiness 1 minute
 UseEntryGuards 0
 RunAsDaemon 1