Changes between Version 8 and Version 9 of UserGuide/BandwidthTweaking


Ignore:
Timestamp:
Feb 28, 2010 11:39:56 PM (8 years ago)
Author:
andar
Comment:

Fix typo

Legend:

Unmodified
Added
Removed
Modified
  • UserGuide/BandwidthTweaking

    v8 v9  
    5757You 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. 
    5858 
    59 || Maximum Download Speed || -1 || (Let the per-torrent speed by limited by the global settings.) || 
    60 || Maximum Upload Speed || -1 || (Let the per-torrent speed by limited by the global settings.) || 
     59|| Maximum Download Speed || -1 || (Let the per-torrent speed be limited by the global settings.) || 
     60|| Maximum Upload Speed || -1 || (Let the per-torrent speed be limited by the global settings.) || 
    6161 
    6262You 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.