[or-cvs] [metrics/master] Update TODO list.

[karsten at seul.org]

Author: Karsten Loesing <karsten.loesing at gmx.net>
Date: Sun, 12 Jul 2009 17:27:37 +0200
Subject: Update TODO list.
Commit: 3560da529f4ea2b115e1d1d2bf485c85ce9e213a

---
 TODO |   37 +++++++++++++++++++------------------
 1 files changed, 19 insertions(+), 18 deletions(-)

diff --git a/TODO b/TODO
index 66f8acb..0c60414 100644
--- a/TODO
+++ b/TODO
@@ -30,19 +30,14 @@ Tasks for July:
    . Determine v2/v3 share as average over complete period, not only at the
      end of a period.
    . Try to find out why some directories write empty geoip-stats files.
-   - Figure out why estimations are that far off. Where is the flaw in the
-     math?
    . Add numbers about failed directory requests to the stats.
-   - Gather statistics about download times and timeouts, so that we can
-     infer the distribution of available bandwidth at clients, possibly per
-     country. For a first estimate, measure transmission times of directory
-     downloads using Apache as proxy. In the long term, measure
-     transmission times directly in Tor to include clients downloading via
-     the ORport and include aborted downloads (with a threshold of 50% or
-     2 minutes?).
+   . Gather statistics about download times and timeouts, so that we can
+     infer the distribution of available bandwidth at clients.
    - Require DirReqStatistics config option, warn if DirPort is set to 0.
    - Analyze directory requests by end of July which are running for about
      two months by then.
+   - Figure out why estimations are that far off. Where is the flaw in the
+     math?
 
  . Cells in circuit queues
    o Consider circuits that were active in the past 15 minutes rather than
@@ -58,30 +53,32 @@ Tasks for July:
      single value in Java. Does this result in similar results produced by
      Java as by Tor?
 *  o May 31: Prepare buffer-stats patch for inclusion in master.
+*  o June 30: Decide if buffer statistics should be measured in the future
+*    in aggregate form.
    . Run on gabelmoo and have some other folks run the patch; analyze
      results for "1.2, new circuit window sizes. make the default package
      window lower" and "2.1, squeeze loud circuits" in performance roadmap.
-*  - June 30: Decide if buffer statistics should be measured in the future
-*    in aggregate form.
+*  - July 31: Write report on measured cell stats data.
 
  . Clients connecting to entry nodes
 *  o May 31: Implement entry-guard statistics in Tor.
+*  o June 30: Decide if statistics should be measured in the future in
+*    aggregate form.
    o Get patch into master.
    . Run patch on gabelmoo and a few other places.
-*  - June 30: Decide if statistics should be measured in the future in
-*    aggregate form.
+*  - July 31: Write report on measured entry stats data.
 
  . Exiting traffic by port
    o Write outgoing traffic by port to logs.
    o Include patch in master.
-   . Ask 1 or 2 volunteers suggested by Roger to run the patch.
-*  - May 31: Run on one of Jake's nodes.
+*  o June 30: Decide if statistics should be measured in the future in
+*    aggregate form.
+*  . May 31: Run on a few exit nodes.
    . Consider a threshold of bytes per port (possibly as percentage of
      overall bytes) for including a port. Otherwise stats are too big for
      extra-info documents.
-   - Evaluate data together with Steven.
-*  - June 30: Decide if statistics should be measured in the future in
-*    aggregate form.
+*  - July 31: Evaluate data together with Steven. Write report on measured
+*    exit port data.
 
  o Measure throughput
    o Evaluate torperf run and see if such runs should be performed
@@ -89,6 +86,7 @@ Tasks for July:
    o Handle timeouts better by catching INT signals and writing an error
      message to stdout.
    o Set up second torperf installation somewhere, possibly on moria.
+*  - July 31: Write report on measured throughput data.
 
  o Directory archives
    o Set up dedicated database server somewhere; goals are better
@@ -196,6 +194,9 @@ Tasks for September:
      on dynamic IP addresses.
    - Investigate assumption that 1 IP address is equivalent to 1 user;
      consider dynamic IP addresses and NAT, too.
+   - Add statistics to analyze failure types of directory requests and
+     include transmission times of failed requests exceeding a certain
+     threshold of 50% of all bytes.
 
  - Cells in circuit queues
    - Extend statistics to medians, and 1st/9th deciles; problematic as
-- 
1.5.6.5