10-28-04 10:45 PM
In article <799gd.131$aJ.4953@typhoon.bart.nl>, sss@sssss.ss says...
> John Smith wrote:
>
> Because I don't know exactly what is involved? I am not /that/ much
> of a genius :-) As far as I understand it, the http-requests get bounced
> a few times between tor-servers, but twenty or thirty seconds seems a
> bit excessive. Half of the URLs I address time out before connection
> is made and I am on cable.
>
>
>
Any proxy will be slower than direct connect purely because it has extra
hops to go through. The way a proxy works is that you request the data,
it goes and gets it, downloads it and uploads it to you (and if a
filtering proxy it will download/rewrite/upload). All those extra steps
guarantee it will be slower than direct connect in nearly all instances
(one instance it may not be is if a route from you to the site is
buggered, but from the proxy to the site is fine and you to the proxy is
also fine).
The biggest impact on speed is the number of users, they all share the
bandwidth. So, taking Tor as the example, if one of the hops in Tor is
on a 3 MB pipe, but there are thousands of users going through that,
then each user is only going to get a very small fraction of that speed.
The more users, the slower it gets unless more resources/bandwidth are
added on the proxy side. With Tor that means as more use it as clients,
it will get slower unless more also run servers.
There are far more factors that will affect your perceived speed through
a proxy, the above is a simplistic explanation, but it should give you a
good idea of why it is slower.
/steve
--
Check out Cotse's Privacy Watch.
A comprehensive information resource.
http://www.cotse.net/privacy/
[ Post a follow-up to this message ]
|