tor-webwml.git

1) ## translation metadata
2) # Revision: $Revision$

3) # Translation-Priority: 4-optional

4) 
5) #include "head.wmi" TITLE="Metrics Project: Measuring the Tor Network"
6) 
7) <div class="main-column">
8) 
9) <!-- PUT CONTENT AFTER THIS TAG -->
10) 
11) <h2>Metrics Project: Measuring the Tor Network</h2>
12) <hr />
13) 
14) <p>

15) The Metrics Project aims at measuring various aspects of the Tor network,
16) including both contributed resources and network usage. These information
17) are important, e.g., for deciding what parts of the network require more
18) support to better meet user needs.

19) </p>
20) 
21) <p>

22) There are at least three aspects of the Tor network which shall be
23) considered in this project:

24) </p>
25) 
26) <ul>

27) <li><b>Relays:</b> There are already statistics covering the data that
28) relays report about themselves and which are confirmed in parts by the
29) directory authorities. The <a
30) href="http://torstatus.kgprog.com/">TorStatus</a> project evaluates the
31) hourly published directories containing lists of all running relays and
32) keeps track of their uptimes and advertised bandwidths. However, an
33) aggregate view of the development of relays over an extended period of time
34) is still missing. In addition to that, all information about provided
35) bandwidth capacity as reported by the relays is not necessarily
36) trustworthy. There has not been a comprehensive measurement of relay

37) performance so far to validate bandwidth claims and relay stability.</li>

38) <li><b>Bridges:</b> A special type of relays is running as bridges. Bridges
39) are relaying traffic, too, but are not listed in the public directory. The
40) purpose of bridges is to allow censored clients to connect to the Tor
41) network without their censor being able to prohibit access easily. The
42) number and capacity of bridges is therefore not publicly known and has not

43) been evaluated, yet.</li>

44) <li><b>Clients:</b> Little is known about usage of the Tor network. In
45) particular, the number and location of clients are largely unknown. A rough
46) estimation is that there are a few hundreds of thousands of clients in the
47) network; a number which is very hard to verify. There are no recent studies
48) on the number of Tor users which would help obtaining a better picture on
49) usage of the Tor network. Clearly, all investigations of clients need to be
50) performed with special care and in highly aggregated form to protect users'

51) anonymity.</li>

52) </ul>
53) 
54) <p>

55) The Metrics Project is planned to run for three years from September 2008
56) to August 2011 (see section 5.7 of the <a
57) href="https://svn.torproject.org/svn/tor/trunk/doc/roadmaps/2008-12-19-roadmap-full.pdf">three-year
58) development roadmap</a> for more details). Milestones are scheduled for
59) every six months in this period. The following sections (yet only one) show
60) progress made in these milestones.

61) </p>
62) 
63) <h3>February 2009</h3>
64) 
65) <p>

66) The first milestone of the Metrics Project is intended to evaluate public
67) data about the Tor network, like network statuses and router descriptors.
68) These evaluations

69) shall help decide what data will be needed in the future to measure
70) contribution to and usage of the Tor network. The following results are

71) already available. <a href="<page contact>">Feedback</a> is very welcome!

72) </p>
73) 
74) <ul>

75) <li>Evaluation of Relays from Public Directory Data (<a

76) href="https://git.torproject.org/checkout/metrics/master/report/dirarch/dirarch-2009-06-22.pdf">PDF</a>,
77) 558K, last updated on June 22, 2009).</li>

78) <li>Analysis of Bridge Usage in Tor (<a

79) href="https://git.torproject.org/checkout/metrics/master/report/bridges/bridges-2009-06-22.pdf">PDF</a>,
80) 76K, last updated on June 22, 2009).</li>

81) <li>Evaluation of Client Requests to the Directories to determine total numbers
82) and countries of users (<a
83) href="https://git.torproject.org/checkout/metrics/master/report/dirreq/directory-requests-2009-06-25.pdf">PDF</a>,
84) 207K, last updated on June 25, 2009).</li>

85) 

86) <li>All scripts and sources used in these evaluations (not the data,
87) unfortunately) are available in a public Git repository that can be cloned
88) using the following command:<br /> <tt>git clone

89) git://git.torproject.org/git/metrics/</tt></li>

90) </ul>
91) 

92) <h3>August 2009</h3>
93) 
94) <p>
95) The second milestone focuses on both network and performance metrics.
96) </p>
97) 
98) <ul>
99) <li>Possible problems of directory authorities assigning Stable and Guard flags (<a

100) href="https://git.torproject.org/checkout/metrics/master/report/dirarch/relayflags-2009-04-01.pdf">PDF</a>,
101) 2M from April 1, 2009).</li>

102) <li>Simulation of the number of Fast, Stable, and Guard flags for changed
103) requirements (<a

104) href="https://git.torproject.org/checkout/metrics/master/report/dirarch/flagrequirements-2009-04-11.pdf">PDF</a>,
105) 229K from April 11, 2009).</li>

106) </ul>
107)