Anti Leech System

[Katzius]

Hello,
I have been using qBitorrent for quite some time now with no issues but this:
before I start, I have to say that I am paying monthly for a seedbox service which I use to upload most of the torrents I am downloading and keeping my ratio in most the torrent sites,torrentleech, torrentday, etc... very high, much above 5.0, Which I think is more than enough.
Now, I live in Israel and we have a very poor upload bandwidth(about 10kbps) here, hence the reason I am paying for a seedbox.
I am using NetLimiter to limit the upload of certain application in Windows. Once I limit the upload of qBitorrent for less than 5 Kbps, the download rate goes down substantially.
I think people who are "leechers" will find a way around this or just use other client.
Is there anyway to turn this "Anti Leech" system off?
I mean come on if I would want to leech I would use other torrent client whom their anti leech system aren't working as good as qBitorrent(such as uTorrent)
of course Open source is the best!
I also have to add that once the torrent client uses more than 80% of my upload bandwidth(8 kbps) it completely take over the download bandwidth which kinda make the internet unusable.

Thank you and much appreciated.

[sledgehammer_999]

This isn't an anti-leech feature. You are limiting the upload speed too much. Even when you are downloading you NEED to communicate with other peers. If you don't communicate with other peers fast enough your download speeds will drop. eg a peer needs to know when you finished with one piece in order to send you the other. or it needs to negotiate with you a connection on tight timeouts...

Try disabling "apply rate limit to transport overhead". This might help.
PS: I constantly run with a 10KB/s upload limit and my downloads are fine. -- see I am always a leecher --

[Katzius]

Thanks a lot for the reply.

I have disabled that feature a while ago, had no effect on this matter.
And you are probably right, but I think, 4 kbps should be much more than enough just to receive/send information about the package and not the package itself. I mean like which pieces completed etc.
But I guess I will have to accept it and limit it to 5 kbps.

I would like to ask another question and I am not quite sure if I should open another thread for that.
The torrents I am usually downloading are comperessed into alot of files. Once the download is finished, I obviously extract the files to a folder and later delete all the rar files and keep the files that were extracted.
After I finish all I mentioned above and restart qBittorent client, the client performs an automated file size check and auto start downloading the files and I just completed.
I have looked around in this forum for an answer, but found one with your(sledgehammer)
http://qbforums.shiki.hu/index.php?topic=1704.0
this thread is from a year ago,
Wanted to know if there's anyway around this?
Thank you

[sledgehammer_999]

Well if you delete the compressed files, what did you expect? qbt will notice and start redownloading. You can pause the torrents prior to exiting qbt. In this case qbt will still notice that the files are missing but will not start downloading.

As for 4KB/s thing. Well if you connect or try to connect to a lot of peers it creates a lot of chit-chat between your client and the other clients. And I think, the faster the download the faster you need to communicate to organize the next payload, otherwise speed drop.

[Peter]

http://www.bitthief.ethz.ch/

Enjoy?

What Sledge said is also important. Upload is not only used for uploading data, but for other communications as well.
There are torrents that I could not even download without removing my limits.

Why don't you download the files from your seedbox via FTP or SFTP?

[Katzius]

I am actually finding myself doing that a lot, but it is kinda of an hassle to download the torrent and log in to the seed box control panel and then upload the torrent to the seedbox client, and only after it finishes(12Mbps download rate) I can then download it with an ftp.
the above process is a bit annoying for small torrents, useful for the big ones.
Well I guess all of you are right about the chit-chat between the peers, because I notice qBittorent display 0kbps upload but Netlimiter shows otherwise, I guess that is the communication between the peers.
But still I think there's an optimization issue with qBittorrent regarding this process(communication between the peers) because I tried limiting uTorrent client to basically 0 upload limit and it did NOT effect the download rate what so ever. and not to mention that NetLimiter was correlated with the upload rate that uTorrent shows(zero) unlike qBittornet which apparently doesn't take that "chit-chat" in consideration when displaying the upload rate at any given moment.

P.S thank for the recommendation about BitThief, sounds a very interesting project I will check it, not doubt it.

[Nemo]

Nah.. I don't think that there is an optimization issue with communication between the peers at all. Sorry to say but the location that you are in with your very slow internet especially your upload speed thats an issue, with all due respect of course.

qBittorrent is not a leecher client and just like most of the clients out there setting a low upload speed can result in a low download speed. If you want it otherwise you can try bad leecher mods, at your own risk. Therefore this isn't something that you can enable/disable. Its not something that you can control.

If your upload speed is set too high, it will eat into your download speed; a setting too low may result in other peers dropping your connection or limiting the data they’re sending to you. Finding a harmonized balance between the two is the key. The general rule of thumb is to select an upload rate that is about 80% of your upload speed

I've read somewhere that if you set an upload speed between 1-5KB/s that your download speed also gets decreased a lot.

Remember, when you download torrents, your upload speed is what matters, not download speed.

[Peter]

[quote="Katzius"]I tried limiting uTorrent client to basically 0 upload limit and it did NOT effect the download rate[/quote]

W-w-w-w-haaaaat?
You limited the upload via NetworkMeter or some software to ZERO and it WORKED?
How the ... there was something wrong there. I'm 99.99999% sure.
That cannot work. Even download generates upload. That's just... no. Nope.

How did you check it's actual speed tho? (This made me curious now. I used 5kbps, and even that slowed down downloads sometimes.)

By the way. SFTP is encrypted. So if you download that way, you cannot be tracked down, unlike via regular torrenting. That's also a huge selling point for anti-freedom / anti-privacy countries (US, now UK, France and all).

[Katzius]

[quote="shiki"]
[quote="Katzius"]I tried limiting uTorrent client to basically 0 upload limit and it did NOT effect the download rate[/quote]

W-w-w-w-haaaaat?
You limited the upload via NetworkMeter or some software to ZERO and it WORKED?
How the ... there was something wrong there. I'm 99.99999% sure.
That cannot work. Even download generates upload. That's just... no. Nope.

How did you check it's actual speed tho? (This made me curious now. I used 5kbps, and even that slowed down downloads sometimes.)

By the way. SFTP is encrypted. So if you download that way, you cannot be tracked down, unlike via regular torrenting. That's also a huge selling point for anti-freedom / anti-privacy countries (US, now UK, France and all).
[/quote]



NetLimiter obviously doesn't function in this case as firewall and doesn't blocks all the outgoing connections, so if I take a close look at netlimiter I could see that uTorrent still send some data out even when I set the limit to 0, but it didn't go above 1kbps at any given point, and it did not effect the download speed at all...
I can certainly understand what you guys are saying, in order to download piece of information you have to send information back that's obvious but I think you can agree with me that amount is not only determined by that protocol itself(torrent or w/e) I guess the software it self as some implementation on the data it need to send in order to continue to download.
Unfortunately I am not yet a computer programmer or understands internet protocols and communication all that well, but I am trying to learn as much as possible.
But I guess it doesn't need to send a lot of bits of information, just like a few line of text of information, I could be mistaken though

[sledgehammer_999]

The netlimiter does it monitor udp connections too or just tcp connections?
When you limit to 0, are most of the peer connections in utorrent uTP or BT connections (you can see it in the peers tab in the IP column at the end of the IP)

[Switeck]

TCP/IP networking handles dropped packets and corrupted packets, which requires considerable bandwidth overheads both on download and upload side.
Even when no packets are lost or corrupt, those overheads can be 3-10% of the size of the data.

http://stackoverflow.com/questions/3613 ... s-requests

[ciaobaby]

Can I just say;

IF you have to micro-manage your data transfer to that degree, you are either using the wrong ISP or you should NOT be running peer to peer clients in the first place.

Transport overhead with TCP/IP is NECESSARY, so  if you don't want the "waste" of dropped packets or overhead that TCP (Not HTTP) can create, may I dis-respectfully suggest you use a BT client that allows you to use UDP ONLY, which does NO parity checking or error control  of any kind.

[sledgehammer_999]

[quote="ciaobaby"]suggest you use a BT client that allows you to use UDP ONLY, which does NO parity checking or error control  of any kind.
[/quote]

That's why I asked about udp. It is conceivable that in his situation utorrent when setting an upload limit of 0 it only uses uTP connections which rely on udp protocol.

[Switeck]

uTorrent's early uTP implementations used tiny data payload packets which while downloading resulted in upload-side overheads being about 25% of the total download speed. (150 byte data payload size and no use of aggregate ACKs is my guess why.)
Even the more optimized uTP that uTorrent uses now may be using smaller data packets than TCP does (1200 vs ~1400) which might result in more overheads due to each packet's overheads. Aggregate ACKs can make up some of the difference, but not every uTP-using BT client supports that.

Overheads for qBitTorrent are worse if you are using/enabled this:
DHT, Local Peer/Seed Discovery, Peer EXchange, many connected peers/seeds, lots of upload slots, lots of torrents active, lots of trackers on each torrent, always announce on all trackers, exchange trackers with peers, high half-open rate in qBT, resolve peers names/countries, embedded tracker.

[ciaobaby]

verheads for qBitTorrent are worse if you are using/enabled this: ....

So is uTorrent "overhead" if you have those 'features' enabled.