Deluge Forum

Hi there,

waffles.fm and what.cd are both banning deluge from their trackers from monday 22 Feb. You could say now: who cares? I don't know these trackers even.

The staff is claiming that they found out by diagnosing their torrent swarms that deluge on average downloads 15.4% more data then the actual torrent size and that this is highly ineffecient for their swarms.

Deluge will be removed from the whitelist. After performing an analysis on our swarms, we found that over 4088 downloads, deluge downloaded, on average, 15.4% more data than the size of the torrent.

Why they don't get in touch with developers first...? I don't know. I find this quite annoying and thought this might interest some people here.

Regards
JanAcc

I was just about to post this. Glad I checked first.

I want to see what the Deluge devs think about this. This is the first I've heard about Deluge reporting more to the tracker than you have actually downloaded. And I refuse to change clients just because What/Waffles says it's so.

So what do the devs have to say about this? You guys ever seen anything like this happen? And if it actually is happening, hopefully a fix will be released as soon as possible.

I read through some of the discussions on their forums. It seems to be clear that this a deluge specific thing and not soemthing due to libtorrent because several other clients (e.g., rtorrent) using libtorrent don't have this issue.

What sounds pretty reasonable to me was this post:

Deluge is a decision in my opinion, there shouldn't be any need to ban it. It basically is the seedbox client since it is an aggressive downloader (that's why it downloads more than it needs, it simultaneously downloads from multiple seeds/peers for the same piece so lots gets junked). I might as well just stop using my seedbox for auto (again, a personal decision to use, some may hate it but it is an effective way to build ratio). In rtorrent I rarely seed to 1, and in deluge I seed to 2-5 ratio on all V0. Just voicing my opinion that it shouldn't be banned.

But I don't have this much insight... I would be curious what some of the deluge devs have to say...


EDIT:
I just read these two posts of an admin on waffles:

For Deluge, it's a time sink for a different reason. A LOT of users are reporting incorrect download stats, and after checking a few random accounts, a significant portion are suffering the same problem. The ban on Deluge is only temporary until a fix is issued. We have staff on hand at both sites researching this, just like we helped the Transmission dev hunt down and destroy its incorrect stat reporting.

[...] so I'm going to create a bounty. First person to make a tool that converts Vuze's xml data, adds the torrents to µTorrent, and updates µTorrent's resume.dat with the location of the already downloaded data, and open sources it, shall receive a week of free leech to claim at will. [...] A conversion from Deluge is not necessary as its author is already working on a fix (newsflash!).

!?!?
Can anyone confirm this?

First of all, Deluge uses a different form of libtorrent than you're thinking.

rTorrent uses the libtorrent developed by rakshasa.

Deluge uses the libtorrent from rasterbar.

Confusing? Yes, but importantly different.

Deluge downloads redundant data. The libtorrent (rasterbar) protocol allows for over-downloading. In a massive example of oversimplification: It was implemented to overcome peer preferencing in Bitcomet, an app that intentionally favoured other instances of BitComet.

As a result, Deluge actually does download more data than needed, usually 15% or so. This has been addressed, and has been fixed, and the rumour mill is that a Deluge 1.2.1 will depend on the fixed libtorrent (rasterbar.)

So 1.2.1 should fix this problem? If this is true, and the problem is actually fixed, then hopefully W/W will re-allow the client.

Yep, see this:

http://forum.deluge-torrent.org/viewtop ... =7&t=28975

EDIT: Nevermind. Just reloaded Synaptics and deluge-gtk now appears. I'm now on 1.2.1.

Im still having the same problem with overdownloading. Even after upgrading to 1.2.1.

Any ideas?

Check to see that you are using libtorrent 0.14.9 or greater.