Squeezing non-relays at the entry node

Mike Perry mikeperry at fscked.org
Mon Feb 22 06:48:35 UTC 2010

Thus spake Roger Dingledine (arma at mit.edu):

> Hi folks (Nick in particular),
> I've been pondering other performance improvements. One of them is to
> rate-limit client connections as they enter the network. Rate limiting
> in the Tor client itself would work better, but it's not a very stable
> equilibrium -- it encourages people to switch to security disasters
> like tortunnel.
> It would impact Mike's bwauthority tests. We'd want to make an exception
> for those Tors. I think we'd leave the torperf deployments alone, since
> after all their goal is to measure "realistic" client performance.

Has code been checked in to handle this case? Otherwise any
experiments you run will be tainted by the bias of the bandwidth
authorites effiectively being disabled, for better or worse.

Also, my opinion is that eventually this value should be set by the
bandwidth authorites. They already measure a network-wide average
stream capacity. It seems to me that this should be the value we cap
long term client streams at, if it turns out that this experiment
improves overall performance. 

It does feel like a hack to compensate for poor flow control to me,

Mike Perry
Mad Computer Scientist
fscked.org evil labs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20100221/b5093bf8/attachment.pgp>

More information about the tor-dev mailing list