Changes between Version 2 and Version 3 of UserGuide/BandwidthTweaking


Ignore:
Timestamp:
02/19/2010 05:14:57 AM (11 years ago)
Author:
pi3832
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UserGuide/BandwidthTweaking

    v2 v3  
    33The settings below are suggestions.  They are intended to give users more guidance than the settings recommended in the FAQ, but are by no means definitive. 
    44 
    5 '''Don't be greedy.'''  There's more content out there than you can ever consume.  You don't need to download it all ''right now! ''  By allocating your bandwidth properly you can maintain a solid, thick stream of data that fills up your hard-drive 10-times faster than you'd expect. 
     5The best rule to remember is: '''Don't be greedy.'''  There's more content out there than you can ever consume.  You don't need to download it all ''right now! ''  By allocating your bandwidth properly you can maintain a solid, thick stream of data that fills up your hard-drive 10-times faster than you'd expect.  Maximizing your peak download rates can be fun and all, but it doesn't necessarily get you the best over-all performance. 
    66 
    7 Maximizing your peak download rates can be fun and all, but it doesn't necessarily get you the best over-all performance. 
     7So, as a subsidiary rule, there's this: ''More is not always better.''  It rarely works to just crank everything to [http://www.youtube.com/watch?v=ll7rWiY5obI#t=1m18 11].  So, while the settings suggested below may seem low, they should give better results over time. 
    88 
    99=== Determine Internet connection speed === 
     
    1313!SpeedTest.net will give you results in Mbps (Mb/s).  Multiply those results by 122 to get your connection speed in KiB/s, which are the units used in the Preferences->Bandwidth window.  (At least they are for v1.2.0 for Linux.) 
    1414 
    15 === Preferences -> Bandwidth === 
     15=== Preferences: Bandwidth === 
    1616 
    1717==== Global Settings ==== 
    1818 
    19 || Maximum Connections || -1 || (Let the per-torrent settings limit the number of connections.) || 
    20 [[BR]] 
    21 || For upload speeds of: || < 50 KiB/s || 50 - 150 KiB/s || 150 - 250 KiB/s || > 250 KiB/s || 
    22 || Maximum Upload Slots || 2 * || 4 * || 7 * || 10 * || 
    23 [[BR]] 
    24 || Maximum Download Speed || 80 - 95% of tested download speed || (Be careful of setting this too high--it can strangle your browsing, media streaming, etc. and other people who use your connection.) 
    25 || Maximum Upload Speed || 80% of tested upload speed || (Upload speed is the real limiter for most things internet--beware guarantees of huge download speeds that don't mention upload speeds.) || 
    26 || Maximum Half-Open Connections: || 50 - 100 || (Unless you've got a Windows install with limited half-open connections.  Then this should be 50 - 80% of that limit.) || 
     19|| Maximum Connections || '''250''' || (You may never see this many connections depending on your per-torrent and active-torrent limits.) || 
     20|| Maximum Upload Slots || '''-1''' || (Let the per-torrent and active-torrent settings limit this.) || 
     21|| Maximum Download Speed || '''80 - 95%''' of tested download speed || (Be careful of setting this too high--it can strangle your browsing, media streaming, etc. and other people who use your connection.) 
     22|| Maximum Upload Speed || '''80%''' of tested upload speed || (Upload speed is the limiter for most p2p applications.) || 
     23|| Maximum Half-Open Connections: || '''50 - 100''' || (Unless you've got a Windows install with limited half-open connections.  Then this should be 50 - 80% of that limit.) || 
    2724 
    28 Everyone got all excited when it was discovered that Microsoft had, at one point, limited half-open connections in XP and Vista to small numbers.  As a plethora of hacks came out to remove this limit, somehow "half-open connections" became the scape-goat for slow download speeds.  As people hacked around the limit, and as Microsoft removed it in later release, it seemed that, if limited half-open connections is bad, then lots and lots of them must be good.  Not really, though.   
     25Everyone got all excited when it was discovered that Microsoft had, at one point, limited half-open connections in XP and Vista to small numbers.  As a plethora of hacks came out to remove this limit, somehow "half-open connections" became the scape-goat for slow download speeds.  Suddenly it became ''de riguer'' to advise Windows users to hack the TCP/IP driver and set their half-open connections to something huge, like 200. 
    2926 
    30 Half-open connections should either resolve to fully-opened connections or be timed-out.  So, you really don't need to allow that many of them to be hanging around. 
     27Most users have no need for a setting that high, and Microsoft has removed the original limit in later releases/patches--or at least made it user-adjustable.  Half-open connections should--rapidly--resolve to fully-opened connections or be timed-out.  So, you really don't need to allow that many of them to be hanging around. 
    3128 
    32 || Maximum Connection Attempts per Second || 20 || (You don't need to fill all your allowed connections in the first second, do you?) || 
     29|| Maximum Connection Attempts per Second || '''20''' || (When you set your per-torrent connections and such to a reasonable number, you will fairly quickly establish reliable connections with plenty of peers.  You shouldn't need to be banging around for thousands of new connections every minute.) || 
    3330 
    3431 
    3532==== Per Torrent Settings ==== 
    3633 
    37 || For upload speeds of: || < 50 KiB/s || 50 - 150 KiB/s || 150 - 250 KiB/s || > 250 KiB/s || 
    38 || Maximum Connections || 30 || 50 || 100 || 200 || 
    39 || Maximum Upload Slots || 2 || 4 || 7 || 10+ || 
     34|| ''For upload speeds of:'' || < 50 KiB/s || 50 - 150 KiB/s || 150 - 250 KiB/s || > 250 KiB/s || 
     35|| Maximum Connections  || 30 || 50 || 80 || 120 || 
     36|| Maximum Upload Slots || 4  || 5  || 7  || 8  || 
    4037 
    41 While a basic premise of bit-torrenting is the "swarm" of peers, with more being better, you, as a single client, can spread yourself too thin.  You're more helpful to the swarm by feeding a limited number of peers with a steady, healthy stream of data, than you are by trickling out data to a huge number of peers. 
     38While a basic premise of bit-torrenting is a big-ol' "swarm" of peers, you, as a single client, can spread yourself too thin.  You're more helpful to the swarm by feeding a limited number of peers with a steady, thnick stream of data, than you are by spraying out droplets of data to a huge number of peers. 
    4239 
    43 You should limit your upload slots based on your upload speeds to make sure that each connected peer is getting a reasonable amount of bandwidth. 
     40So, you should limit your upload slots based on your upload speeds to make sure that each connected peer is getting a reasonable amount of bandwidth. 
    4441 
    45 You should limit your number of connections, because it does take resources to keep track of each connection, and why track connections that are giving you, relatively, minor speeds?  One peer feeding you 5 KiB/s is worth 50 peers flickering at 0.1 KiB/s.  (Why are there so many 0.1 KiB/s feeds out there?  Perhaps because too many people aren't setting their "upload slots" correctly?) 
    46  
    47 You also don't want/need to be keeping track of a large number of peers waiting to leech when you have limit upload slots. 
     42You should limit your number of connections because it take resources to keep track of each connection, and why track connections that are giving you a trickle if any data?  One peer feeding you 5 KiB/s is worth 50 peers flickering at 0.1 KiB/s.  Similarly, you don't want/need to be keeping track of a large number of peers waiting around hoping one of your upload slots comes free. 
    4843 
    4944|| Maximum Download Speed || -1 || (Let the per-torrent speed by limited by the global settings.) || 
    5045|| Maximum Upload Speed || -1 || (Let the per-torrent speed by limited by the global settings.) || 
    5146 
    52 You can, by setting the per-torrent maximums to less than the global maximums, prevent a single torrent from using up all the allocated bandwidth and forcing all of the other (auto-managed) torrents to pause.  But there is no advantage to increasing your number of active torrents.  Indeed, by letting the torrent with the best speeds dominate, it will finish as quickly as possible and then stop competing at all for resources with the other torrents in the queue. 
     47You can, by setting the per-torrent maximums to less than the global maximums, prevent a single torrent from using up all the allocated bandwidth and forcing all of the other (auto-managed) torrents to pause.  But there is no advantage to increasing your number of active torrents.  Indeed, by letting the torrent with the best speeds dominate, it will finish as quickly as possible and then stop competing for resources with the other torrents in the queue. 
    5348 
    5449 
    55  
    56 === Preferences -> Queue === 
     50=== Preferences: Queue === 
    5751 
    5852==== Active Torrents ==== 
    5953 
    60 || For upload speeds of: || < 50 KiB/s || 50 - 150 KiB/s || 150 - 250 KiB/s || > 250 KiB/s || 
    61 || Total active || || || || || 
    62 || Total active downloading || || || || || 
    63 || Total active seeding: || || || || || 
     54|| ''For upload speeds of:'' || < 50 KiB/s || 50 - 150 KiB/s || 150 - 250 KiB/s || > 250 KiB/s || 
     55|| Total active             || 3 || 5 || 10 || 15 || 
     56|| Total active downloading || 3 || 4 || 8  || 10 || 
     57|| Total active seeding:    || 3 || 5 || 10 || 15 || 
    6458 
    65 All downloading torrents are automatically also seeding.  This means that the ''actual'' number of maximum seeding torrents the number of "active seeding" '''plus''' "active downloading." 
     59By setting "active downloading" less than the "total active" you can make sure that you are seeding completed torrents at all times. 
    6660 
    67 So, if you have limited bandwidth, you can end up strangling your active seeds by having too many active downloads. 
     61Deluge always prioritizes downloads over uploads, so seeding can be set the same as total but all of your downloading slots will still get used. 
     62 
     63 ''Note'': All downloading torrents are automatically also seeding. 
     64 
     65=== Example Results === 
     66 
     67|| Assumed upload speed (KiB/s)     || 25  || 50  || 150 || 250 || 
     68|| Total active torrents            || 3   || 5   || 10  || 15  || 
     69|| Maximum upload slots per torrent || 4   || 5   || 7   || 8   || 
     70|| Maximum total upload slots       || 12  || 25  || 70  || 120 || 
     71|| Worst-case KiB/s per upload slot || 2.1 || 2.0 || 2.1 || 2.1 || 
     72|| Worst-case KiB/s per torrent     || 8.3 || 10  || 15  || 17  ||