[tor-commits] [tech-reports/master] Change style of performance roadmap to tortechrep.

[karsten at torproject.org]

commit a2f3f956422ccc77d5cf056ced9192cef285dea3
Author: Karsten Loesing <karsten.loesing at gmx.net>
Date:   Thu Aug 30 12:03:36 2012 +0200

    Change style of performance roadmap to tortechrep.
    
    Also update a few URLs and make minor tweaks.
---
 2009/performance/performance.tex |   51 ++++++++++++++++++++------------------
 2009/performance/tortechrep.cls  |    1 +
 2 files changed, 28 insertions(+), 24 deletions(-)

diff --git a/2009/performance/performance.tex b/2009/performance/performance.tex
index f75d83c..69cebd2 100644
--- a/2009/performance/performance.tex
+++ b/2009/performance/performance.tex
@@ -1,12 +1,13 @@
-\documentclass{article}
+\documentclass{tortechrep}
+%\documentclass{article}
 %\usepackage{palatcm}
-\usepackage{fancyhdr}
+%\usepackage{fancyhdr}
 \usepackage{color}
 \usepackage{graphicx}
-\usepackage{fullpage}
-\setlength{\headheight}{12pt}
-\setlength{\headsep}{12pt}
-\addtolength{\textheight}{-24pt}
+%\usepackage{fullpage}
+%\setlength{\headheight}{12pt}
+%\setlength{\headsep}{12pt}
+%\addtolength{\textheight}{-24pt}
 
 \usepackage{prettyref}
 \newrefformat{sec}{Section~\ref{#1}}
@@ -16,8 +17,8 @@
 \newrefformat{eqn}{Equation~\ref{#1}}
 \newrefformat{apx}{Appendix~\ref{#1}}
 
-\usepackage{hyperref}
-\hypersetup{colorlinks, citecolor=MyDarkRed, filecolor=MyDarkBlue, linkcolor=MyDarkRed, urlcolor=MyDarkBlue}
+%\usepackage{hyperref}
+%\hypersetup{colorlinks, citecolor=MyDarkRed, filecolor=MyDarkBlue, linkcolor=MyDarkRed, urlcolor=MyDarkBlue}
 
 \definecolor{MyDarkBlue}{rgb}{0, 0.0, 0.45}
 \definecolor{MyDarkRed}{rgb}{0.45, 0.0, 0}
@@ -37,21 +38,24 @@
 \newcommand{\ia}{inter alia\xspace}
 \makeatother
 
-\newcommand{\thetitle}{Performance Improvements on Tor}
-\title{\thetitle\\or,\\Why Tor is slow and what we're going to do about it}
+\title{Performance Improvements on Tor\\
+or,\\Why Tor is slow and what we're going to do about it}
 
 %% Please add your name in here if you contribute
-\author{Roger Dingledine \and Steven J. Murdoch}
+\author{Roger Dingledine and Steven J. Murdoch}
+\contact{arma at torproject.org,steven.murdoch at cl.cam.ac.uk}
+\date{November 9, 2009}
+\reportid{2009-11-001}
 
-\pagestyle{fancy}
-\fancyhf{}
+%\pagestyle{fancy}
+%\fancyhf{}
 
-\fancyhead[C]{\thetitle}
-\fancyfoot[C]{\thepage}
+%\fancyhead[C]{\thetitle}
+%\fancyfoot[C]{\thepage}
 
 \begin{document}
 
-\thispagestyle{plain}
+%\thispagestyle{plain}
 
 \maketitle
 
@@ -131,9 +135,9 @@ network fast enough to handle everyone who wants to use it, we've ordered
 the sections by precedence. That is, solving the earlier sections will
 be necessary before we can see benefits from solving the later sections.
 
-\pagebreak
+%\pagebreak
 \tableofcontents
-\pagebreak
+%\pagebreak
 
 \section{Tor's congestion control does not work well}
 \label{sec:congestion}
@@ -567,7 +571,7 @@ Advocacy and education is especially important in the context of new and
 quickly-changing government policies. In particular, the data retention
 question in Germany is causing instability in the overall set
 of volunteers willing to run relays. Karsten's latest
-metrics\footnote{\url{https://www.torproject.org/projects/metrics}}
+metrics\footnote{\url{https://metrics.torproject.org/}}
 show that while the number
 of relays in other countries held steady or went up during 2008, the
 numbers in Germany went down over the course of 2008. On the other hand,
@@ -706,8 +710,8 @@ might fail to give back the `real' content, requiring users to repeat
 their connection attempts.
 
 Mike has been working on tools to
-identify these relays: SpeedRacer\footnote{\url{https://svn.torproject.org/svn/torflow/trunk/README.PerfMeasurements}}
-and SoaT\footnote{\url{https://svn.torproject.org/svn/torflow/trunk/NetworkScanners/README.ExitScanning}}.
+identify these relays: SpeedRacer\footnote{\url{https://gitweb.torproject.org/torflow.git/blob/HEAD:/NetworkScanners/BwAuthority/README.BwAuthorities}}
+and SoaT\footnote{\url{https://gitweb.torproject.org/torflow.git/blob/HEAD:/NetworkScanners/ExitAuthority/README.ExitScanning}}.
 Once the tools are further refined, we should be able to figure out if
 there are general classes of problems (load balancing, common usability
 problems, etc) that mean we should modify our design to compensate. The
@@ -1378,7 +1382,7 @@ better performance, but we can also dynamically adapt our paths away
 from overloaded relays.
 
 Mike and Fallon wrote a
-proposal\footnote{\url{https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/151-path-selection-improvements.txt}}
+proposal\footnote{\url{https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/151-path-selection-improvements.txt}}
 explaining the details of how to collect the stats, how many data points
 the client needs before it has a good sense of the expected build times,
 and so on.
@@ -1511,7 +1515,7 @@ blog post on the topic provides background and
 details\footnote{\url{https://blog.torproject.org/blog/overhead-directory-info\%3A-past\%2C-present\%2C-future}}.
 
 Proposal 158 further reduces the directory overhead, and is scheduled
-to be deployed in Tor 0.2.2.x.\footnote{\url{https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/158-microdescriptors.txt}}
+to be deployed in Tor 0.2.2.x.\footnote{\url{https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/158-microdescriptors.txt}}
 
 {\bf Impact}: Low for normal users, high for low-bandwidth users.
 
@@ -1768,7 +1772,6 @@ well as feature-oriented funding.
 
 % Mike Perry provided many of the ideas discussed here
 
-\bibliographystyle{acm}
 \bibliography{performance}
 
 \end{document}
diff --git a/2009/performance/tortechrep.cls b/2009/performance/tortechrep.cls
new file mode 120000
index 0000000..4c24db2
--- /dev/null
+++ b/2009/performance/tortechrep.cls
@@ -0,0 +1 @@
+../../tortechrep.cls
\ No newline at end of file