Here's how to find out which measurement is limiting your relay: Relay bandwidth can be limited by a relay's own observed bandwidth, or by the directory authorities' measured bandwidth. Relays outside North America and Western Europe are usually slower. Relays transiting via Comcast have been slow at times. Check the Internet peering (bandwidth, latency) from your relay's provider to other relays.Others can be viewed using top or similar tools. Check RAM, CPU, and socket/file descriptor usage on your relay.Other times, it is the network that is slow: the relay has bad peering to most other tor relays, or is a long distance away. Sometimes, a relay is slow because its processor is slow or its connections are limited. Then Tor would be almost as fast as the wider Internet). (We want enough relays to so that each relay is loaded at 10%. This is good for clients: an overloaded relay has high latency. It's normal for most relays to be loaded at 30%-80% of their capacity.
So even if all relay operators set their advertised bandwidth to their localĬonnection speed, we would still need bandwidth authorities to balance the loadīetween different parts of the Internet.
So we need to know how well each relay can connect to the entire world. Most providers tell you the maximum speed of your local connection.īut Tor has users all over the world, and our users connect to one or two Guard relays at random. It will have diagnostics for relays that don't get measured, and relays that have low measurements.
We're working on a new bandwidth scanner, which is easier to understand and maintain. Tor wants low-latency web pages, which requires fast connections with headroom.īitTorrent wants bulk downloads, which requires using all the bandwidth. It does a reasonable job for most relays.īut Tor's goals are different to protocols like BitTorrent. Tor manages bandwidth across the entire network.
0 kommentar(er)
