Changes between Version 22 and Version 23 of doc/FireFoxTorPerf


Ignore:
Timestamp:
Apr 23, 2010, 4:47:54 AM (9 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/FireFoxTorPerf

    v22 v23  
    22
    33== Introduction ==
    4 
    54Tor is known for being secure but slow. If you want to improve browsing speed a bit, please follow the following simple instructions for tweaking the Firefox web browser's settings:
    65
    76== Procedure 1 ==
    8 
    97First, open Firefox's advanced settings menu by running ''about:config'' from the address bar. Upon entering this address, you will see a long list of internal settings. Modify the following ones and set them to the suggested values shown here for maximum performance:
    108
    11 {{{ network.http.keep-alive.timeout:600 (300ms default is OK usually, but 600 is better.)
     9{{{
     10network.http.keep-alive.timeout:600 (300ms default is OK usually, but 600 is better.)
    1211network.http.max-persistent-connections-per-proxy:16 (Default is 4)
    1312network.http.pipelining:true (Default- false. Some old HTTP/1.0 servers can't handle it.)
    1413network.http.pipelining.maxrequests:8 (No default)
    1514network.http.proxy.keep-alive:true (Default- true, but double check)
    16 network.http.proxy.pipelining:true (Default- false) }}}
    17 
    18 Afterwards, just restart the browser and experience the difference! For some automated additional performance hacks, check out [http://www.totalidea.com/freestuff4.htm FireTune]. Currently, Fire``Tune is only for Win32, but you can do the same tweaks manually with the help of [http://www.tweakfactor.com/articles/tweaks/firefoxtweak/4.html this page]. Additionally, there is the [http://fasterfox.mozdev.org/ FasterFox extension] that is easy to install, and is also '''platform independent'''!
     15network.http.proxy.pipelining:true (Default- false) - see Proecedure 2 below.}}}
     16Afterwards, just restart the browser and experience the difference! For some automated additional performance hacks, check out [http://www.totalidea.com/freestuff4.htm FireTune]. Currently, Fire{{{}}}Tune is only for Win32, but you can do the same tweaks manually with the help of [http://www.tweakfactor.com/articles/tweaks/firefoxtweak/4.html this page].
    1917
    2018== Procedure 2 - an update and addendum to Procedure 1 ==
    21 
    2219These results were arrived at empirically, using the win32 bundle, Tor & Privoxy & Vidalia bundle: 0.1.2.5-alpha
    2320
    24 You will need the following tools...
    25  * [http://freehaven.net/~squires/torbutton/ Tor Button]
    26  * [http://fasterfox.mozdev.org/ FasterFox]
    27  * [http://www.prnwatch.com/prio.html Prio (win32)]
     21 * [https://torbutton.torproject.org/ Tor Button]
     22 * [http://https://addons.mozilla.org/en-US/firefox/addon/4420 Configuration Mania for Firefox]
    2823 * [http://www.speedguide.net/downloads.php TCPOptimizer (win32)]
    2924 * [http://www.speedguide.net/read_articles.php?id=1497 Event ID 4226 Patcher (win32)]
     25 * DNS Latency
    3026
    31 == Tor Button - enable / disable TOR access in FireFox ==
     27=== Tor Button - enable / disable Tor access in FireFox ===
    3228This provides an optional button or text in the bottom right of the browser window in Firefox. This allows you to switch Tor on and off.
    3329
    34 == FasterFox - Modify performance related settings in FireFox ==
    35 This plugin modifies the networking and cache settings for Firefox. The following settings need to be modified.
    36  * Initially you need to select 'Custom' in the FasterFox Options. This allows you to use your own detailed options, rather than the default schemes supplied.
    37  * Select the Cache tab.
    38   * Enter a Memory Cache Capacity of >= 8mb
    39   * Enter a Disk Cache Capacity of >= 8mb
    40  * Select the Connection tab
    41   * Enter Max Connection >= 128
    42   * Enter Max Connection Per Server >= 10
    43   * Enter Max Persistent Connection Per Server >= 8
    44   * Enter Max Persistent Connection Per Proxy >= 8
    45  * Select the Pipelining tab
    46   * Ensure all 3 tick options are enabled
    47   * Enter Max pipelining requests >= 10
     30=== Configuration Mania - Modify performance related settings in FireFox ===
     31This plugin modifies the networking and cache settings for Firefox. When you load Configuration Mania, select the HTTP Network settings tab.
    4832
    49 == Prio - Increase Tor process Priority (win32) ==
    50 You will also realise a substantial increase in performance by increasing the process priority for the Tor process. You can do this in Task Manager after you identify tor.exe. If you want to persist the process priority you will need a Task Manager addon. An effective tool for doing this is [http://www.prnwatch.com/prio.html Prio]. This tool can only be used in a non-commercial setting, unless you license it.
    51 I dont recommend modifying the process above 'high'. If Tor crashes or freezes windows will become unresponsive. Setting it to 'Above Normal' is a good start.
     33    * TOR does not work well with HTTP1.1. Ensure HTTP 1.1 is disabled for proxy connections.
     34    * TOR does not work well with pipelining. Ensure this option is not enabled for proxy connections.
     35    * TOR does not work well with Persistent HTTP connections. Ensure this option is disabled for proxy connections.
    5236
    53 == TCP/IP - Optimise 2K/XP's throughput (win32) ==
    54 Windows XP has a self-tuning IP stack, but it can still benefit from a little help. Using the TCP Optimiser tool from above you can tune the RWIN, SACK OPTS (rfc 2038), and tcp1323opts controlling window scaling. The tool has one button optimise. This setting is sufficient to benefit from immediate increases to Tor throughput. To increase throughput further you can try experimenting with lower values of the IP TTL (Time To Live). Values as low as 32 will work and result in improved performance.
     37NOTE: Do not use page prefetching. Disable this if it is enabled. Prefetching is a speculative feature, which assumes that you will read the pages referenced by the links in the current page you are viewing. This places undue load on the TOR network. Its unlikely you will read all the pages referenced by the current page, especially in the case of search engines result
    5538
    56 == Remove the limit on TCP connection attempts XP SP2 (win32) ==
     39=== TCPOptimizer -  2K/XP's throughput (win32) ===
     40Windows XP has a self-tuning IP stack, but it can still benefit from a little help. Using the TCP Optimiser tool from above you can tune the RWIN, SACK OPTS (rfc 2038), and tcp1323opts controlling window scaling. The tool has one button optimise. This setting is sufficient to benefit from immediate increases to Tor throughput. To increase throughput further you can try experimenting with lower values of the IP TTL (Time To Live). Values as low as 32 will work and result in improved performance. Also try experimenting with smaller TCPWindowSizes. This setting is automatically adjusted when you move the slider marked 'Connection Speed' of the TCPOptimizer  tool.
     41
     42=== Event ID 4226 Patcher - Remove the limit on TCP connection attempts XP SP2 (win32) ===
    5743[http://www.speedguide.net/read_articles.php?id=1497 Remove the limit on TCP connection attempts] SpeedGuide.net has an interesting article detailing this restriction introduced in XP SP2. Microsoft have restricted the amount of half-open TCP/IP connections with the proviso that it would reduce the pace that worms spread. As noted by SpeedGuide, internet worms spread isotropically (multi-directionally) and so their infecton rate is exponential. As such, placing a constant (limit) on the rate of connection creation for every computer running XP SP2 will slow the rate of worms spreading (for that group of computers) but not by much. Consider the population of humans on the planet. Its over ~6 billion.
    5844
    59 Supposing all these people are running Windows XP SP2, with rate limited half-open connections. To infect the entire population of computers would take:
    60 We are assuming optimum forward infection here. In the first second we have infected 10 machines. The 2nd second to elapse will cause (10 x 10) + 10 = 110 computers to be infected. The 3rd second to elapse would cause:
    61  ( (10 * 10) * 10 ) + (10 * 10) =  1100 computers to be infected. So the number of computers infected for every second that elapses is :
    62  computers infected = ~ 10 ^ elapsedSeconds
     45Supposing all these people are running Windows XP SP2, with rate limited half-open connections. Rate limiting is set to 10 half-open connections per second. To infect the entire population of computers would take: We are assuming optimum forward infection here. In the first second we have infected 10 machines. The 2nd second to elapse will cause (10 x 10) + 10 = 110 computers to be infected. The 3rd second to elapse would cause:
    6346
     47 . ( (10 x 10) x 10 ) + (10 * 10) + 10 =  1110 computers to be infected. So the number of computers infected for every second that elapses is : computers infected = ~ 10 ^ elapsedSeconds
    6448In 12 seconds, we would have 10 ^ 12 = 1 billion computers infected. Full infection occurs before 13 seconds have elapsed !
    6549
    66 This is all skewed by network topologies and routing algorithms, but they would affect a non-limited network in an identical manner. So the affect is a theoretical minimum of 12 seconds of additional notice to act against the worm. To all intents and purposes, this is useless.
     50This is all skewed by network topologies and routing algorithms, but they would affect a non-limited network in an identical manner. So the affect is a theoretical maximum of 13 seconds of additional notice to act against the worm. To all intents and purposes, this is useless.
    6751
    6852Of much more interest is the effect on ANY network that relies on many open connections, such as Tor and a host of P2P applications. The effect here is a slow down of communications, with the limit acting as the catalyst.
     
    7054Use the Event ID 4226 Patcher to mitigate against this.
    7155
    72 == DNS - reducing latency ==
    73 For faster DNS performance generally and with TOR(on win32 only i'm afraid) see...
    74  * [http://www.analogx.com/contents/download/network/fc.htm AnalogX - FastCache]
    75 When TOR starts it will report if it is using localhost to resolve DNS addresses. When you install FastCache, it sets up a local, cached and persistent store of DNS addresses. DNS resolves cost TOR a lot in terms of latency. A large part of TOR's reduction in speed is caused by setting up the path to the Onion routers that are servicing the request. Reduce DNS latency and the time cost of setting up the TOR channels are reduced.
    76 Also for all OS'es see...
    77  * [http://www.opendns.com/ OpenDNS]
     56=== DNS Latency - Reducing Latency ===
     57You can use [http://www.opendns.org OpenDNS] to reduce your DNS latency for all operating systems.
    7858
     59== Procedure 3 - A Tor SLA (Service Level Agreement) ==
     60If you follow the previous authors work you should have well performing access. To go that bit further lets consider the ideal behaviour of our Tor client.
     61
     62You will need: [https://www.torproject.org/tor-manual.html.en The on-line reference to Tor properties, that can be placed in torrc.] Always back up this file before editing.
     63
     64Lets think of a Service Level requirement we might like to place on our Tor client.
     65
     66 * we want it to establish circuits as quickly as possible. If it takes too long ignore them, by timing out the building of circuits quickly.
     67 * now we have circuit build time-outs occuring more frequently as we don't wait too long for circuits to establish, we need to encourage Tor to try to generate circuits more often.
     68 * Once we have established a circuit, we are assuming its a good one and we dont want it being timed out by firewalls or anything else. We need to make sure a ping occurs on the circuit to prevent this.
     69Given this SLA, lets come up with some properties that may help satisfy it.
     70
     71 * CircuitBuildTimeout NUM
     72  . Try for at most NUM seconds when building circuits. If the circuit isn't open in that time, give up on it. (Default: 1 minute.) Force circuits that are quick to establish and thus likely to push traffic more quickly. Values as low as 2 seconds have been tried with good results, although the author is not sure on the effect on anonymity.
     73 * KeepalivePeriod NUM
     74  . To keep firewalls from expiring connections, send a padding keepalive cell every NUM seconds on open connections that are in use. If the connection has no open circuits, it will instead be closed after NUM seconds of idleness. (Default: 5 minutes)
     75 * NewCircuitPeriod NUM
     76  . Every NUM seconds consider whether to build a new circuit. (Default: 30 seconds) Lets make Tor ready to establish a new circuit more readily.
     77{{{
     78# This file was generated by Tor; if you edit it, comments will not be
     79# preserved The old torrc file was renamed to torrc.orig.1 or similar,
     80# and Tor will ignore it
     81# The advertised (external) address we should use.
     82#Address DELIBERATELY LEFT BLANK - LET Tor CALCULATE ON STARTUP
     83# MaxAdvertisedBandwidth N bytes|KB|MB|GB|TB If set, we will not
     84# advertise more than this amount of bandwidth for our BandwidthRate.
     85# Server operators who want to reduce the number of clients who ask
     86# to build circuits through them (since this is proportional to
     87# advertised bandwidth rate) can thus reduce the CPU demands on their
     88# server without impacting network performance.
     89MaxAdvertisedBandwidth 50KB
     90# Administrative contact information to advertise for this server.
     91ContactInfo NAME at ISP dot com
     92# Try for at most NUM seconds when building circuits. If the circuit
     93# isn't open in that time, give up on it. (Default: 1 minute.)
     94CircuitBuildTimeout 5
     95# If set, Tor will accept connections from the same machine (localhost
     96# only) on this port, and allow those connections to control the Tor
     97# process using the Tor Control Protocol (described in control-spec.txt).
     98ControlPort 9051
     99# Serve directory information from this port, and act as a directory
     100# cache.
     101DirPort 9030
     102# Send a padding cell every N seconds to keep firewalls from closing
     103# our connections while Tor is not in use.
     104KeepalivePeriod 60
     105# Where to send logging messages.  Format is:
     106# Log minSeverity[-maxSeverity] (stderr|stdout|syslog|file FILENAME).
     107Log notice stdout
     108# Force Tor to consider whether to build a new circuit every NUM
     109# seconds.
     110NewCircuitPeriod 15
     111# Set the server nickname.
     112Nickname YOURNICKNAME
     113# Advertise this port to listen for connections from Tor clients and
     114# servers.
     115ORPort 9001
     116# Let a socks connection wait NUM seconds unattached before we fail
     117# it. (Default: 2 minutes.)
     118SocksTimeout 30
     119# If we have keept a clean (never used) circuit around for NUM
     120# seconds, then close it. This way when the Tor client is entirely
     121# idle, it can expire all of its circuits, and then expire its TLS
     122# connections. Also, if we end up making a circuit that is not useful
     123# for exiting any of the requests we're receiving, it won't forever
     124# take up a slot in the circuit list. (Default: 1 hour.)
     125CircuitIdleTimeout 600
     126# If UseEntryGuards is set to 1, we will try to pick a total of NUM
     127# routers as long-term entries for our circuits. (Defaults to 3.)
     128#NumEntryGuards NUM
     129NumEntryGuards 8
     130}}}
    79131== The proof is in the pudding ==
     132With the changes made from Procedure 2 and 3, and a 2Mb connection, you can realise a sustained throughput of >100k, peaking at ~256k, with a ping response time of between 250 and 900ms.
    80133
    81 With the changes made from Procedure 2, you can realise a sustained throughput of >100k, peaking at ~200k or more. These figures are based on the highest TOR bandwidth settings (>1.5mbps), through a 2mb connection. You will also experience much lower DNS latency in general. TOR at version 0.1.2.x uses an Asynchronous DNS resolver, the DNS tips above positively affect TOR traffic.
     134These figures were arrived at by using [http://speedtest.net SpeedTest.net]