[tor-commits] [tech-reports/master] Update bridge-scaling report to new style.

[karsten at torproject.org]

commit 1b501533ea9a17e8ac752a516f48c23f7e95572c
Author: Karsten Loesing <karsten.loesing at gmx.net>
Date:   Tue Aug 7 19:43:34 2012 +0200

    Update bridge-scaling report to new style.
---
 2012/bridge-scaling/bridge-scaling.tex |   21 +++++++++++----------
 2012/bridge-scaling/tortechrep.cls     |    1 +
 2 files changed, 12 insertions(+), 10 deletions(-)

diff --git a/2012/bridge-scaling/bridge-scaling.tex b/2012/bridge-scaling/bridge-scaling.tex
index 6da0964..20a577c 100644
--- a/2012/bridge-scaling/bridge-scaling.tex
+++ b/2012/bridge-scaling/bridge-scaling.tex
@@ -1,12 +1,13 @@
-\documentclass{article}
+\documentclass{tortechrep}
 \usepackage{url}
-\usepackage[pdftex]{graphicx}
-\usepackage{graphics}
-\usepackage{color}
+\usepackage{graphicx}
 \begin{document}
-\title{What if the Tor network had 50,000 bridges?}
-\author{Karsten Loesing\\{\tt karsten at torproject.org}}
 
+\title{What if the Tor network had 50,000 bridges?}
+\author{Karsten Loesing}
+\contact{karsten at torproject.org}
+\reportid{2012-03-001}
+\date{March 9, 2012}
 \maketitle
 
 \section{Introduction}
@@ -14,7 +15,7 @@
 The current bridge infrastructure relies on a central bridge authority to
 collect, distribute, and publish bridge relay descriptors.
 There are currently 1,000 bridges running in the Tor network.\footnote{%
-\url{https://metrics.torproject.org/network.html#networksize}}
+\url{https://metrics.torproject.org/network.html\#networksize}}
 We believe the current infrastructure can handle up to 10,000 bridges.
 Potential performance bottlenecks include:
 
@@ -51,7 +52,7 @@ descriptors with fixed references to disk.
 Figure~\ref{fig:bridgescaling} shows the results.
 
 \begin{figure}[t]
-\includegraphics[width=\textwidth]{bridge-scaling-graph.pdf}
+\includegraphics[width=0.9\textwidth]{bridge-scaling-graph.pdf}
 \caption{Results from load-testing BridgeDB and metrics-db}
 \label{fig:bridgescaling}
 \end{figure}
@@ -67,7 +68,7 @@ hosts.
 These tarballs have substantial overlap.
 If we have tens of thousands of descriptors, we would want to get smarter
 at sending diffs over to BridgeDB and metrics-db.\footnote{See comment at
-\url{https://trac.torproject.org/projects/tor/ticket/4499#comment:7}}
+\url{https://trac.torproject.org/projects/tor/ticket/4499\#comment:7}}
 
 The middle graph shows how long BridgeDB takes to load descriptors from a
 tarball.
@@ -107,7 +108,7 @@ increase in bridges?
 Tonga still does a reachability test on each bridge every 21~minutes or so.
 Eventually the number of TLS handshakes it's doing will overwhelm its
 CPU.\footnote{%
-\url{https://trac.torproject.org/projects/tor/ticket/4499#comment:7}}
+\url{https://trac.torproject.org/projects/tor/ticket/4499\#comment:7}}
 
 We're not sure how to test such a setting, or at least without running 50K
 bridges in a private network.
diff --git a/2012/bridge-scaling/tortechrep.cls b/2012/bridge-scaling/tortechrep.cls
new file mode 120000
index 0000000..4c24db2
--- /dev/null
+++ b/2012/bridge-scaling/tortechrep.cls
@@ -0,0 +1 @@
+../../tortechrep.cls
\ No newline at end of file