aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2004-02-02 06:21:15 +0000
committerNick Mathewson <nickm@torproject.org>2004-02-02 06:21:15 +0000
commit8f00a304db757ac7c320d00789a9a80b159b9309 (patch)
tree56496770a1ac984f1a1b5f2fca928e1f2740d758 /doc
parent6f6bfb67e233d89f894af36437d9b8e5868f5ed0 (diff)
downloadtor-8f00a304db757ac7c320d00789a9a80b159b9309.tar
tor-8f00a304db757ac7c320d00789a9a80b159b9309.tar.gz
Third time--is it right now?
svn:r1055
Diffstat (limited to 'doc')
-rw-r--r--doc/tor-design.tex5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/tor-design.tex b/doc/tor-design.tex
index d7e4eec1e..673fdf356 100644
--- a/doc/tor-design.tex
+++ b/doc/tor-design.tex
@@ -1571,10 +1571,11 @@ performance. % Right now the first $500 \times 500\mbox{B}=250\mbox{KB}$
%sendme} acknowledgments arrive.
To quantify these effects, we did some informal tests using a network of 4
nodes on the same machine (a heavily loaded 1GHz Athlon). We downloaded a 60
-megabyte file from {\tt debian.org} every 10 minutes for 21.3 hours (128 sample
+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
+fetching the front page of {\tt cnn.com} (55 kilobytes) every 10 minutes for
+21.3 hours (128 sample points): while a direct
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