commit 779143997c9a4ee8b511a1c9b628942d39e27263 Author: Karsten Loesing <karsten.loesing@gmx.net> Date: Mon Sep 16 10:45:17 2013 +0200 Add feedback from Sathya and Kevin Butler. --- 2013/torperf2/torperf2.tex | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/2013/torperf2/torperf2.tex b/2013/torperf2/torperf2.tex index 6cfbcad..029d8a1 100644 --- a/2013/torperf2/torperf2.tex +++ b/2013/torperf2/torperf2.tex @@ -103,6 +103,23 @@ Fortunately, running client and server on the same physical should not have any effect on measurement results, because all requests and responses traverse the Tor network. +Reasons for \emph{not} separating client and server are: +\begin{itemize} +\item it's easier to deploy client and server together than deploying them +separately and configuring the client to use the server; +\item measurement results can easily contain client and server timestamps +of a measurement; +\item assuming the host has sufficient free bandwidth capacity, measurement +results shouldn't be affected by client and server running on the same +host; and +\item it's not unusual to deploy client and server talking over Tor in a +single tool: think of how a tor relay does bandwidth self-tests to itself. +\end{itemize} + +What's not easily possible with this approach is to configure client and +server to run on different hosts. Is there an experiment where this +might be useful? + \subsubsection{User-defined tor version or binary} A key part of measurements is the tor software version or binary used to @@ -343,7 +360,9 @@ txtorcon for communicating with tor clients, and stem for event parsing. The following list outlines tasks that the new Torperf needs to perform. These could be implemented as Python classes, though this list was not -written with Python or Twisted specifics in mind: +written with Python or Twisted specifics in mind:% +\footnote{An alternative to Python/Twisted might be Go, though it doesn't +have tor controller libs like txtorcon or stem.} \begin{description} \item[configuration handler] Validate and parse configuration file or