Changes between Version 132 and Version 133 of doc/FireFoxTorPerf


Ignore:
Timestamp:
Apr 23, 2010, 10:48:33 AM (9 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/FireFoxTorPerf

    v132 v133  
    3434== FasterFox - Modify performance related settings in FireFox ==
    3535This 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
     36 * You need to select 'Optimized' in the FasterFox Options.
    4837
    4938== Prio - Increase Vidalia / TOR process Priority (win32) ==
     
    7463== DNS - reducing latency ==
    7564For faster DNS performance generally (on win32 only i'm afraid) see...
    76  * [http://www.analogx.com/contents/download/network/fc.htm AnalogX - FastCache]
     65 * [http://www.analogx.com/contents/download/network/fc.htm AnalogX - FastCache] OR
     66 * [http://www.sofotex.com/Outpost-Firewall-download_L5356.html - Agnitum Outpost Firewall]
    7767When 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.
    7868
    79 Having completed testing, TOR addresses do appear in AnalogX FasterCache. FasterCache itself may prove unstable on occasion, with its icon stuck in its 'Red' - problem state. Try it and possibly update this page with your results.
     69Agnitum's Outpost firewall provides a DNS cache and is worth installing just for this feature. In combination you can use another firewall of your choice if you wish. If you choose to use another firewall with Outpost just acting as a DNS cache, make sure you disable all of Outposts additional plugins and all networking modifications that it can make.
     70
     71Having completed testing, TOR addresses do appear in AnalogX FasterCache and Agnitum. FasterCache itself may prove unstable on occasion, with its icon stuck in its 'Red' - problem state. Try it and possibly update this page with your results.
    8072
    8173--- N.B. the effect of FasterCache on TOR is still undetermined, although the 'DNS latency reduction' theory still applies.
     
    9789 * CircuitBuildTimeout NUM
    9890    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.)
    99     Set this to 15 seconds, forcing circuits that are quick to establish and thus likely to push traffic more quickly.
     91    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.
    10092
    10193 * KeepalivePeriod NUM
    10294    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)
    103     We'll set this to 60 seconds.
    10495
    10596 * NewCircuitPeriod NUM
    10697    Every NUM seconds consider whether to build a new circuit. (Default: 30 seconds)
    107     We'll set this to 3 seconds, so TOR is more ready to establish a new circuit.
     98    Lets make TOR ready to establish a new circuit more readily.
    10899
    109100The values to populate torrc with are as follows.
    110  * CircuitBuildTimeout 15
     101 * CircuitBuildTimeout 10
    111102 * KeepalivePeriod 60
    112  * NewCircuitPeriod 3
     103 * NewCircuitPeriod 15 (or try values as low as 2)
    113104
    114105== Bringing it all together - a typical configuration file for Windows ==
     
    120111# The advertised (external) address we should use.
    121112#Address DELIBERATELY LEFT BLANK - LET TOR CALCULATE ON STARTUP
    122 
    123113# Limit the maximum token buffer size (also known as burst) to the given
    124114# number of bytes.
    125 BandwidthBurst 8MB
     115BandwidthBurst 8192KB
    126116
    127117# A token bucket limits the average incoming bandwidth on this node to the
    128118# specified number of bytes per second.
    129 BandwidthRate 8MB
     119BandwidthRate 4096KB
    130120
    131121#MaxAdvertisedBandwidth N bytes|KB|MB|GB|TB If set, we will not advertise more than this amount of bandwidth for our BandwidthRate. Server operators who want to reduce the number of clients who ask to build circuits through them (since this is proportional to advertised bandwidth rate) can thus reduce the CPU demands on their server without impacting network performance.
     
    135125ContactInfo NAME at ISP dot com
    136126#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.)
    137 CircuitBuildTimeout 30
     127CircuitBuildTimeout 2
    138128
    139129# If set, Tor will accept connections from the same machine (localhost only)
     
    147137# Send a padding cell every N seconds to keep firewalls from closing our
    148138# connections while Tor is not in use.
    149 KeepalivePeriod 30
     139KeepalivePeriod 60
    150140
    151141# Where to send logging messages.  Format is minSeverity[-maxSeverity]
     
    154144
    155145# Force Tor to consider whether to build a new circuit every NUM seconds.
    156 NewCircuitPeriod 1
     146NewCircuitPeriod 15
    157147
    158148# Set the server nickname.
     
    161151ORPort 9001
    162152
    163 # How many processes to use at once for decrypting onionskins. (Default: 1)
    164 NumCPUs 1
    165 
    166153# Let a socks connection wait NUM seconds unattached before we fail it. (Default: 2 minutes.)
    167154SocksTimeout 30
    168 
    169 # For each value in the comma separated list, Tor will track recent connections to hosts that match this value and attempt to reuse the same exit node for each. If the value is prepended with a '.', it is treated as matching an entire domain. If one of the values is just a '.', it means match everything. This option is useful if you frequently connect to sites that will expire all your authentication cookies (ie log you out) if your IP address changes. Note that this option does have the disadvantage of making it more clear that a given history is associated with a single user. However, most people who would wish to observe this will observe it through cookies or other protocol-specific means anyhow.
    170 TrackHostExits .
    171 
    172 # TrackHostExitsExpire NUM Since exit servers go up and down, it is desirable to expire the association between host and exit server after NUM seconds. The default is 1800 seconds (30 minutes).
    173 TrackHostExitsExpire 180
    174155
    175156# If we have keept a clean (never used) circuit around for NUM seconds, then close it. This way when the Tor client is entirely idle, it can expire all of its circuits, and then expire its TLS connections. Also, if we end up making a circuit that is not useful for exiting any of the requests we're receiving, it won't forever take up a slot in the circuit list. (Default: 1 hour.)