Why is Tor slow
Users often complain that the Tor network is slow or has inconsistent speed. This page briefly describes some reasons for affected Tor throughput. Interested readers can also refer to the Tor Project FAQ and relevant research for a more detailed explanation.
Tor Circuits Lengthen the Connections
When navigating to clearnet resources, Tor provides anonymity by building circuits with three relays. So instead of connecting directly to the destination server, a connection is made between each relay of the circuit and this takes more time. In the case of onion services, a six-relay arrangement is used in the connection - three picked by the user and three picked by the onion service.
In addition to using multiple relays, Tor tries to build circuits with relays in different geographical locations. This necessarily causes connections to travel further and slows down the fetching of resources.
Tor relays are run by volunteers  in a decentralized way. Consequently, relays do not have uniform quality; some are big and fast, while others are smaller and slower. As a whole, the network could be faster if it had more capacity. To improve the capacity of the Tor network, users can either run a Tor relay or help existing relays.
Misuse of the Tor Network
Some actors misuse the Tor network, either purposefully or due to a lack of knowledge. For instance, Tor is sometimes used to conduct DDoS attacks. By doing this, the Tor relays are the ones who actually suffer from the attack, instead of the intended target. Some people use peer-to-peer software (like BitTorrent) through Tor which slows down the network for all users. 
- Tor Congestion Control: Tor's mechanism does not work well in combining high-volume (bulk transfer) and low-volume (browsing) streams.
- Excessive User Load: Some users put excessive traffic load on the Tor network relative to their network contributions. Methods of limiting these effects and prioritizing other users need to be implemented. 
- Tor Network Capacity: As noted earlier, the total capacity of the Tor network is insufficient relative to unmet privacy demand. A significant boost in the overall number of relays is required. 
- Tor Load Distribution: Tor's current path selection algorithms do not effectively distribute the network load. The properties of relays need to be more accurately estimated so relays do not become over or under-loaded. 
- Tor Latency Failures: Tor is inefficient in handling connection failures or high / variable latency. Better heuristics to move away from bad circuits and a more uniform latency response is required.
- Directory Information Download Overhead: Users with low bandwidth (like those on cell phones) have to spend too much time downloading directory information. Tor protocols need to be optimized for efficiency.
Whonix Download wiki page Copyright (C) Amnesia <amnesia at boum dot org> Whonix Download wiki page Copyright (C) 2014 Patrick Schleizer <firstname.lastname@example.org> This program comes with ABSOLUTELY NO WARRANTY; for details see the wiki source code. This is free software, and you are welcome to redistribute it under certain conditions; see the wiki source code for details.
This is a wiki. Want to improve this page? Help is welcome and volunteer contributions are happily considered! See Conditions for Contributions to Whonix, then Edit! IP addresses are scrubbed, but editing over Tor is recommended. Edits are held for moderation.
- And hostile actors.
- A large file downloaded through BitTorrent can translate to several hours of browsing for the regular Tor Browser user.
- Roger Dingledine is the co-creator of the first alpha version of Tor.
- As the research is dated, some of these issues may have been fully or partially mitigated by now.
- This may involve targeting specific user profiles (e.g. throttling certain protocols) so the original Tor design of high throughput and good latency properties can be realized.
- Economics suggests increased supply will lead to more users arriving to fill the void.
- Capacity is currently estimated by observing the largest traffic burst seen in the past day. This bandwidth capacity is advertised in the directory information, leading clients to preference their path selection based upon a relay's estimated bandwidth.