Search
Search titles only
By:
Search titles only
By:
Log in
Register
Search
Search titles only
By:
Search titles only
By:
Menu
Install the app
Install
Forums
New posts
All threads
Latest threads
New posts
Trending threads
Trending
Search forums
What's new
New posts
New ads
New profile posts
Latest activity
Free Ads
Latest reviews
Search ads
Members
Current visitors
New profile posts
Search profile posts
Contact us
Latest ads
Bodim.lk out now !
Manoj Suranga Bandara
Updated:
20 minutes ago
Power Lifting Lever Belt
SkullVamp
Updated:
Jun 13, 2026
Ad icon
port.lk Domain for sale
Lankan-Tech
Updated:
Jun 13, 2026
Colombo
Kaduwela - Two Storey House for Sale
dilrasan
Updated:
Jun 11, 2026
Ad icon
Wechat qr verification
Pawan2005
Updated:
Jun 11, 2026
Electronics
Vehicles
Property
Search
Reply to thread
Forums
Computers & Internet
Tips & Tricks
maximum speed from torrents
Get the App
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="kaac11" data-source="post: 1761054" data-attributes="member: 42863"><p>The download speed mostly</p><p>depends on the seeder-to-leecher ratio (SLR). Poor download speed is</p><p>mainly a problem with new and very popular torrents where the SLR is</p><p>low.</p><p></p><p>(Proselytising sidenote: make sure you remember that you did not enjoy the low speed. Seed so that others will not endure the same.)</p><p></p><p>There are a couple of things that you can try on your end to improve your speed:</p><p></p><p></p><p>Do not immediately jump on new torrents</p><p></p><p>In</p><p>particular, do not do it if you have a slow connection. The best speeds</p><p>will be found around the half-life of a torrent, when the SLR will be</p><p>at its highest. (The downside is that you will not be able to seed so</p><p>much. It's up to you to balance the pros and cons of this.)</p><p></p><p></p><p></p><p>Limit your upload speed</p><p></p><p>The upload speed affects the download speed in essentially two ways:</p><p></p><p></p><p>* Bittorrent peers tend to favour those other peers that upload to</p><p>them. This means that if A and B are leeching the same torrent and A is</p><p>sending data to B at high speed then B will try to reciprocate. So due</p><p>to this effect high upload speeds lead to high download speeds.</p><p>*</p><p>Due to the way TCP works, when A is downloading something from B it has</p><p>to keep telling B that it received the data sent to him. (These are</p><p>called acknowledgements - ACKs -, a sort of "got it!" messages). If A</p><p>fails to do this then B will stop sending data and wait. If A is</p><p>uploading at full speed there may be no bandwidth left for the ACKs and</p><p>they will be delayed. So due to this effect excessively high upload</p><p>speeds lead to low download speeds.</p><p></p><p>The full effect is a</p><p>combination of the two. The upload should be kept as high as possible</p><p>while allowing the ACKs to get through without delay. A good thumb rule is keeping the upload at about 80% of the theoretical upload speed.</p><p>You will have to fine tune yours to find out what works best for you.</p><p>(Remember that keeping the upload high has the additional benefit of</p><p>helping with your ratio.)</p><p></p><p>If you are running more than one</p><p>instance of a client it is the overall upload speed that you must take</p><p>into account. Some clients (e.g. Azureus) limit global upload speed,</p><p>others (e.g. Shad0w's) do it on a per torrent basis. Know your client.</p><p>The same applies if you are using your connection for anything else</p><p>(e.g. browsing or ftp), always think of the overall upload speed.</p><p></p><p></p><p>Limit the number of simultaneous connections</p><p></p><p>Some</p><p>operating systems (like Windows 9x) do not deal well with a large</p><p>number of connections, and may even crash. Also some home routers</p><p>(particularly when running NAT and/or firewall with stateful inspection</p><p>services) tend to become slow or crash when having to deal with too</p><p>many connections. There are no fixed values for this, you may try 60 or</p><p>100 and experiment with the value. Note that these numbers are</p><p>additive, if you have two instances of a client running the numbers add</p><p>up.</p><p></p><p></p><p>Limit the number of simultaneous uploads</p><p></p><p>Isn't</p><p>this the same as above? No. Connections limit the number of peers your</p><p>client is talking to and/or downloading from. Uploads limit the number</p><p>of peers your client is actually uploading to. The ideal number is</p><p>typically much lower than the number of connections, and highly</p><p>dependent on your (physical) connection.</p><p></p><p></p><p>Just give it some time</p><p></p><p>As</p><p>explained above peers favour other peers that upload to them. When you</p><p>start leeching a new torrent you have nothing to offer to other peers</p><p>and they will tend to ignore you. This makes the starts slow, in</p><p>particular if, by change, the peers you are connected to include few or</p><p>no seeders. The download speed should increase as soon as you have some</p><p>pieces to share.</p><p></p><p></p><p>Why is my browsing so slow while leeching?</p><p></p><p>Your</p><p>download speed is always finite. If you are a peer in a fast torrent it</p><p>will almost certainly saturate your download bandwidth, and your</p><p>browsing will suffer. At the moment there is no client that allows you</p><p>to limit the download speed, only the upload. You will have to use a</p><p>third-party solution, such as NetLimiter.</p><p></p><p>Browsing was used just as an example, the same would apply to gaming, IMing, etc...</p><p></p><p></p><p>Last But Not Least</p><p>Buy Good Internet Package Which Gives You Rockingg Speed</p></blockquote><p></p>
[QUOTE="kaac11, post: 1761054, member: 42863"] The download speed mostly depends on the seeder-to-leecher ratio (SLR). Poor download speed is mainly a problem with new and very popular torrents where the SLR is low. (Proselytising sidenote: make sure you remember that you did not enjoy the low speed. Seed so that others will not endure the same.) There are a couple of things that you can try on your end to improve your speed: Do not immediately jump on new torrents In particular, do not do it if you have a slow connection. The best speeds will be found around the half-life of a torrent, when the SLR will be at its highest. (The downside is that you will not be able to seed so much. It's up to you to balance the pros and cons of this.) Limit your upload speed The upload speed affects the download speed in essentially two ways: * Bittorrent peers tend to favour those other peers that upload to them. This means that if A and B are leeching the same torrent and A is sending data to B at high speed then B will try to reciprocate. So due to this effect high upload speeds lead to high download speeds. * Due to the way TCP works, when A is downloading something from B it has to keep telling B that it received the data sent to him. (These are called acknowledgements - ACKs -, a sort of "got it!" messages). If A fails to do this then B will stop sending data and wait. If A is uploading at full speed there may be no bandwidth left for the ACKs and they will be delayed. So due to this effect excessively high upload speeds lead to low download speeds. The full effect is a combination of the two. The upload should be kept as high as possible while allowing the ACKs to get through without delay. A good thumb rule is keeping the upload at about 80% of the theoretical upload speed. You will have to fine tune yours to find out what works best for you. (Remember that keeping the upload high has the additional benefit of helping with your ratio.) If you are running more than one instance of a client it is the overall upload speed that you must take into account. Some clients (e.g. Azureus) limit global upload speed, others (e.g. Shad0w's) do it on a per torrent basis. Know your client. The same applies if you are using your connection for anything else (e.g. browsing or ftp), always think of the overall upload speed. Limit the number of simultaneous connections Some operating systems (like Windows 9x) do not deal well with a large number of connections, and may even crash. Also some home routers (particularly when running NAT and/or firewall with stateful inspection services) tend to become slow or crash when having to deal with too many connections. There are no fixed values for this, you may try 60 or 100 and experiment with the value. Note that these numbers are additive, if you have two instances of a client running the numbers add up. Limit the number of simultaneous uploads Isn't this the same as above? No. Connections limit the number of peers your client is talking to and/or downloading from. Uploads limit the number of peers your client is actually uploading to. The ideal number is typically much lower than the number of connections, and highly dependent on your (physical) connection. Just give it some time As explained above peers favour other peers that upload to them. When you start leeching a new torrent you have nothing to offer to other peers and they will tend to ignore you. This makes the starts slow, in particular if, by change, the peers you are connected to include few or no seeders. The download speed should increase as soon as you have some pieces to share. Why is my browsing so slow while leeching? Your download speed is always finite. If you are a peer in a fast torrent it will almost certainly saturate your download bandwidth, and your browsing will suffer. At the moment there is no client that allows you to limit the download speed, only the upload. You will have to use a third-party solution, such as NetLimiter. Browsing was used just as an example, the same would apply to gaming, IMing, etc... Last But Not Least Buy Good Internet Package Which Gives You Rockingg Speed [/QUOTE]
Insert quotes…
Verification
Asuwa dahayen wadi kalama keeyada?
Post reply
Top
Bottom