Changes between Version 205 and Version 206 of doc/FireFoxTorPerf


Ignore:
Timestamp:
Sep 20, 2011, 3:21:24 PM (8 years ago)
Author:
nella
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/FireFoxTorPerf

    v205 v206  
    3636
    3737== Advanced Tuning of Tor  ==
    38 If 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.
     38If you follow the previous authors work you should have well performing access. To go that bit further lets consider the ideal behavior of our Tor client.
    3939
    4040You 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.
     
    4444
    4545 * we want it to establish circuits as quickly as possible. If it takes too long to do this ignore them, by timing out the building of circuits quickly.
    46  * now we have circuit build time-outs occuring more frequently, we need to encourage Tor to try to generate circuits more often.
    47  * 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.
     46 * now we have circuit build time-outs occurring more frequently, we need to encourage Tor to try to generate circuits more often.
     47 * Once we have established a circuit, we are assuming its a good one and we don't want it being timed out by firewalls or anything else. We need to make sure a ping occurs on the circuit to prevent this.
    4848
    4949In order to accomplish this, use the latest tor 0.2.2.x-alpha as circuit based timings are automatic and enabled by default.
     
    9393
    9494=== !TCPOptimizer -  2K/XP's throughput (win32) ===
    95 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.
     95Windows 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 optimize. 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.
    9696
    9797||Windows||in TCP Optimizer||
     
    106106
    107107=== Event ID 4226 Patcher - Remove the limit on TCP connection attempts XP SP2 (win32) ===
    108 [[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.
     108[[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 infection 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.
    109109
    110110Supposing 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: