diff options
| author | Roger Dingledine <arma@torproject.org> | 2004-02-02 06:13:04 +0000 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2004-02-02 06:13:04 +0000 |
| commit | 6ba9b3935dc7da84439a8a580c9226f0a74db147 (patch) | |
| tree | 6445ea3f42f36737c899ae8f1c3f48bc6da0a203 /doc | |
| parent | c8373caac42799ae7599a99863a205353c19abc9 (diff) | |
| download | tor-6ba9b3935dc7da84439a8a580c9226f0a74db147.tar tor-6ba9b3935dc7da84439a8a580c9226f0a74db147.tar.gz | |
put the right numbers in
i'll leave the other phrasing for nick
svn:r1052
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/tor-design.tex | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/tor-design.tex b/doc/tor-design.tex index 57920de22..f598d3965 100644 --- a/doc/tor-design.tex +++ b/doc/tor-design.tex @@ -1575,9 +1575,9 @@ megabyte file from {\tt debian.org} every 30 minutes for 54 hours (108 sample points). It arrived in about 300 seconds on average, compared to 210s for a direct download. We ran a similar test on the production Tor network, fetching the front page of {\tt cnn.com} (55 kilobytes): while a direct -download consistently took about 0.5s, the performance through Tor was highly -variable. Some downloads were as fast as 0.6s, with a median at 2.7s, and -80\% finishing within 5.7s. It seems that as the network expands, the chance +download consistently took about 0.3s, the performance through Tor was highly +variable. Some downloads were as fast as 0.3s, with a median at 2.6s, and +90\% finishing within 6.0s. It seems that as the network expands, the chance of building a slow circuit (one that includes a slow or heavily loaded node or link) is increasing. On the other hand, as our users remain satisfied with this increased latency, we can address our performance incrementally as we |