Changes between Version 44 and Version 45 of doc/FireFoxTorPerf


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

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/FireFoxTorPerf

    v44 v45  
    66== Table of contents ==
    77 * Procedure 1
    8  * Advanced Tuning of Tor
    9  * Advanced Tuning of Polipo
    10  * Advanced Tuning of Privoxy
    11  * Advanced Tuning of Windows
     8 * Procedure 2
    129 * The proof is in the pudding, results
     10 * Advanced Tuning for Windows
    1311
    1412== Procedure 1 ==
     
    2321network.http.proxy.pipelining:true (Default- false) - See NOTE1 below.}}}
    2422
    25 Afterwards, just restart the browser and experience the difference! For some automated additional performance hacks, check out the [[https://addons.mozilla.org/firefox/addon/1269|FasterFox extension]]. You also can do the same tweaks manually with the help of [[http://www.tweakfactor.com/articles/tweaks/firefoxtweak/4.html|this page]].
     23Afterwards, just restart the browser and experience the difference! For some automated additional performance hacks, check out the [https://addons.mozilla.org/firefox/addon/1269 FasterFox extension]. You also can do the same tweaks manually with the help of [http://www.tweakfactor.com/articles/tweaks/firefoxtweak/4.html this page].
    2624
    27 NOTE1: Proxy pipelining may not be well supported by Privoxy. For this reason, you may want to install [[http://www.pps.jussieu.fr/~jch/software/polipo/|Polipo]] and use that instead of Privoxy to get the performance benefits of pipelining. If you use [[https://torbutton.torproject.org/|Torbutton]] (which you should, if you want [[https://www.torproject.org/torbutton/design/#attacks|any anonymity at all]]), all of the Tor-relevant privacy scrubbing features of Privoxy are no longer necessary.
     25NOTE1: Proxy pipelining may not be well supported by Privoxy. For this reason, you may want to install [http://www.pps.jussieu.fr/~jch/software/polipo/ Polipo] and use that instead of Privoxy to get the performance benefits of pipelining. If you use [https://torbutton.torproject.org/ Torbutton] (which you should, if you want [https://www.torproject.org/torbutton/design/#attacks any anonymity at all]), all of the Tor-relevant privacy scrubbing features of Privoxy are no longer necessary.
    2826
    2927NOTE2: 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 and clog your circuits with unnecessary traffic. Its unlikely you will read all the pages referenced by the current page, especially in the case of search engines results.
    3028
    31 === Using Polipo Proxy (example assumes Windows - adjust accordingly) ===
    32 Polipo as a proxy instead of Privoxy has been discussed in some places online, with reports that it is more performant.
    33 To use this proxy:
    34  * Install Polipo to the default location
    35  * Set Vidalia's Proxy application to:
    36     'C:\Program Files\Polipo\polipo.exe' - without quotes.
    37  * Set Vidalia's Proxy application arguments to:
    38     -c "C:\Program Files\Polipo\config"
    39 
    40 You will not see a shell window for Polipo, but the process will be created and visible in the Task Manager. Check the process exists to assure it is working correctly.
    41 
    42 == Advanced Tuning of Tor  ==
     29== Procedure 2 - A Tor Non-Functional Requirement (NFR) ==
    4330If 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.
    4431
    45 You 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.
     32You 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.
    4633
    47 === A Tor Non-Functional Requirement (NFR) ===
    4834Lets think of a Non-Functional Requirement we might like to place on our Tor client.
    4935
     
    5541 * CircuitBuildTimeout NUM
    5642  . 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 this can cause severe damage to the Tor network if your network connection is simply not fast enough to establish any circuits in this time. The effect is a smaller 'Topological Radius' of servers used for Tor, ie the network connections available from your connection. Unfortunately, the smaller you make this number, the smaller the number of paths your client will use, and the less your anonymity.
    57   As of Tor v0.2.1.9-alpha, the CircuitBuildTimeout has been clipped to 30 seconds, which affects some of the tuning recommendations here. From the release notes:"
    58   ''Clip the CircuitBuildTimeout to a minimum of 30 seconds.
    59   Warn the user if lower values are given in the configuration.
    60   Bugfix on
    61   0.1.1.17-rc. Patch by Sebastian.''"
    6243 * NumEntryGuards NUM
    6344  . If we are going to be decreasing the CircuitBuildTimeout, you want to increase the likelihood you have a guard node fast enough to build these fast circuits for you. NUM=5 to 8 are good choices here.
     
    7051{{{
    7152# Try for at most NUM seconds when building circuits. If the circuit
    72 # isn't open in that time, give up on it.
    73 # (Default: 1 minute.)
     53# isn't open in that time, give up on it. (Default: 1 minute.)
    7454CircuitBuildTimeout 5
    7555
    76 # Increase the number of guards to increase the likelihood that
     56# Increase the number of guards to increase the likelihood that 
    7757# you will have a few guards fast enoiugh to build these circuits.
    78 # (Defaults to 3.)
    7958NumEntryGuards 6
    8059
    8160# Send a padding cell every N seconds to keep firewalls from closing
    82 # our connections while Tor is not in use.
    83 # (Default: 5 minutes)
     61# our connections while Tor is not in use. (Default: 5 minutes)
    8462KeepalivePeriod 60
    8563
    8664# Force Tor to consider whether to build a new circuit every NUM
    87 # seconds.
    88 # (Default: 30 seconds)
     65# seconds. (Default: 30 seconds)
    8966NewCircuitPeriod 15
    9067}}}
     
    9269As an added bonus, with these settings the "New Identity" button in Vidalia also effectively becomes a "This circuit is WAY too slow" button that you can mash to get a faster, more responsive circuit if Tor ever starts choking up on you. This is necessary because sometimes circuits will start out fast, but then get overloaded as traffic from other clients bursts and overwhelms the slowest node in the path.
    9370
    94 ----
    95 == Advanced Tuning of Polipo ==
    96 Within Polipo's config file, add the following parameters at the top:
    97 {{{
    98 pipelineAdditionalRequests=yes
    99 maxPipelineTrain=20
    100 serverMaxSlots=16
    101 maxSideBuffering=65536
    102 socksParentProxy=localhost:9050
    103 proxyPort=8118
    104 disableVia=true
    105 censoredHeaders=from,accept-language,x-pad
    106 censorReferer=maybe
    107 allowedClients="127.0.0.1"
    108 ### disk cache below can be disabled by setting it to "": diskCacheRoot=""
    109 diskCacheRoot="/Temp/"
    110 localDocumentRoot=""
    111 proxyName="polipo.example.org"
    112 cacheIsShared = false
    113 }}}
     71== The proof is in the pudding, results ==
     72With the changes made from Procedure 1 and 2, and a 2Mb connection, you can realise a sustained throughput of >100k, peaking at ~256k or more, with a ping response time of between 250 and 900ms.
    11473
    115 The settings above enable Polipo to replace Privoxy, but still enables the Tor toggle button to operate, if you are using the Tor FireFox plugin.
     74These figures were arrived at by using [http://speedtest.net SpeedTest.net]
    11675
    117 
    118 == Advanced Tuning of Privoxy ==
    119 Privoxy is set to be a 'straight-through' proxy server, with the toggle switch. Its buffer is reduced to below that of RWIN. This is because RWIN represents the largest TCP receive window. Its value is chosen to be above Tor default socks size = 252KB
    120 ||Privoxy||config.txt||
    121 || -- || -- ||
    122 ||Privoxy:buffer || 265 (KB)||
    123 ||toggle || 0||
    124 
    125 == Advanced Tuning of Windows ==
     76== Advanced Tuning for Windows ==
    12677This section has been included last for those who are technically capable.
    12778
    128 === Processor Scheduling (win32) ===
    129 Windows enables the program running in the foreground to have heightened processor resources. If this option is switched to 'Background Processes', Tor appears to return consistently higher performance. This option can be found in 'My Computer | Right click | Properties | Advanced Tab | Performance Settings | Advanced tab again.
     79=== TCPOptimizer -  2K/XP's throughput (win32) ===
     80Windows 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.
    13081
    131 === TCPOptimizer -  2K/XP's throughput (win32) ===
    132 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 MTU, 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.
    133 
    134 ||Windows||in TCP Optimizer||
    135 || -- ||-- ||
    136 ||RWIN|| TCPOptimizer max setting||
    137 ||MTU|| 576, 1500 or 1492 - try all 3 settings||
    138 ||Window Scaling|| On||
    139 ||TcpIP TTL || 128 (hops)||
    140 ||LANBufferSize || 65535 (bytes)||
    141 
    142 You can view your connection parameters and their effects on your connections, both with Tor and without Tor, at [[http://www.dslreports.com/tweaks|DSLReports]]
     82You can view your connection parameters and their effects on your connections, both with Tor and without Tor, at [http://www.dslreports.com/tweaks DSLReports]
    14383
    14484=== Event ID 4226 Patcher - Remove the limit on TCP connection attempts XP SP2 (win32) ===
    145 [[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.
     85[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.
    14686
    14787Supposing 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:
     
    15696Use the Event ID 4226 Patcher to mitigate against this.
    15797
    158 === DNS Catching time ===
     98
     99The following parameters must also satisfy the formula below for optimal performance.
     100
     101''Windows:RWIN >= Privoxy:buffer > ( Tor:ConstrainedSockSize default = 262KB )''
     102
     103||Windows||in TCP Optimizer||
     104|| -- ||-- ||
     105||RWIN || TCPOptimizer max setting||
     106||Window Scaling|| On||
     107||TcpIP TTL || 128 (hops)||
     108||LANBufferSize || 65535 (bytes)||
     109----
    159110Reducing DNS caching time reduces the risk of an invalid DNS resolve, given Tor servers may be operating in a DHCP environment that updates the IP each time the network connects.
    160111||Windows||registry:TCPIP service||
    161112|| -- || -- ||
    162113||DNS Cache || 36000(seconds (10 hours)) set in registry by hand, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters||
    163 
    164 == The proof is in the pudding, results ==
    165 With the changes made from Procedure 1 and 2, and a 2Mb connection, you can realise a sustained throughput of >100k, peaking at ~256k or more, with a ping response time of between 250 and 900ms. In other words, experimentation away from default settings, should enable you to saturate your internet connection (depending on Tor node capacity), which is the ideal result. All results tested under Tor v0.1.2.7-alpha(r17216)
    166 
    167 These figures were arrived at by using [[http://speedtest.net|SpeedTest.net]]
     114----
     115Privoxy is set to be a 'straight-through' proxy server, with the toggle switch. Its buffer is reduced to below that of RWIN. This is because RWIN represents the largest TCP receive window. Its value is chosen to be above Tor default socks size = 252KB
     116||Privoxy||config.txt||
     117|| -- || -- ||
     118||Privoxy:buffer || 265 (KB)||
     119||toggle || 0||
    168120
    169121CategoryHowTos