[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] r18863: {projects} scribble notes on section 5 items. to be fleshed out later. (projects/performance)
Author: arma
Date: 2009-03-10 09:27:12 -0400 (Tue, 10 Mar 2009)
New Revision: 18863
Modified:
projects/performance/performance.tex
Log:
scribble notes on section 5 items. to be fleshed out later.
Modified: projects/performance/performance.tex
===================================================================
--- projects/performance/performance.tex 2009-03-10 13:05:58 UTC (rev 18862)
+++ projects/performance/performance.tex 2009-03-10 13:27:12 UTC (rev 18863)
@@ -1165,8 +1165,10 @@
% entry guard'', so removing any of the hops seems like a bad move.
% But YMMV.
-\section{Better handling of high/variable latency and failures}
+\section{Clients need to handle variable latency and failures better}
+
+
\subsection{Our round-robin and rate limiting is too granular}
Tor's rate limiting uses a token bucket approach to enforce a long-term
@@ -1238,12 +1240,35 @@
rate-limiting in mind.
\subsection{The switch to Polipo: prefetching, pipelining, etc}
+
+Polipo makes Tor appear faster, for some web browsing activities. Yay.
+We should continue our plans to migrate to it.
+
\subsection{better timeouts for giving up on circuits and trying a new one}
+
+Proposal 151 and friends.
+
\subsection{when a circuit has too many streams on it, move to a new one}
+
+This would prevent any single circuit from getting too overloaded.
+
+But actually, this idea would benefit high-volume flows most, so
+it is a bad idea. We should not do it.
+
\subsection{If extending a circuit fails, try extending a few other
places before abandoning the circuit.}
+
+This should cut down on the total number of extend attempts in the
+network, which is good since some of our other schemes involve increasing
+that number.
+
\subsection{Bundle the first data cell with the begin cell}
+This would be great for latency and time-to-page-starts-getting-rendered.
+But it's hard because socks wants the handshake to complete before you're
+allowed to send data. we could hack polipo to optimistically send it
+anyway, since we ship with polipo. seems like a risky move. but quite a
+good payoff.
\section{Network overhead too high for modem users}