qBittorrent official forums

After downloading 100MB from the swarm I want to give back 150MB (150% ratio). Now I must manually pause this job because qbt wants to upload ~6GB! This is definitely wrong!

[quote="gwarser"]
After downloading 100MB from the swarm I want to give back 150MB (150% ratio). Now I must manually pause this job because qbt wants to upload ~6GB! This is definitely wrong!
[/quote]

Well we have a stale mate and I don't know how to solve it. If I actually do the calculation as upload/download=ratio I'll have the other problem. If I don't, I'll have your problem.

Would this be a good place to point out that I did suggest that 'fudging' the ratio number would be a problem at some point?



....

No? okay thought not ... Cheery-bye

IMO, these are 2 opposite edge cases.
Not fudging the numbers: Let's say a user imports his fully downloaded torrent and wants to share it until ratio 1.5. However, since he will never download anything the all_time_download var will be 0. So the ratio will appear as MAX_RATIO+1 (aka 10000) which is bigger than 1.5. That means that he will never seed that torrent.

That means that he will never seed that torrent.

How??
All it takes is to set the task to "No ratio set" then check the tracker account occasionally, because it does NOT matter what "ratio" that is shown in the client, it is what the ratio that the TRACKER has that really counts.

Don't change the criteria of my hypothesis. I said the user has set in the options(under bittorrent) a share ratio limit of 1.5.
Of course the true ratio is logged by the tracker. However, the ratio presented by the client is (mostly) just a way to auto-manage his seeding.
Unfortunetaly there are corner cases such as this, that need manual intervention.

[quote="sledgehammer_999"]
If you experience "freezing of the gui" try using the below build made using boost 1.55. (please report if you still experience freezing UI)
http://builds.shiki.hu/temp/qbittorrent ... _setup.exe
[/quote]

Thanks Sledge, i will test it out and let you know. The freezes seem to happen sporadicly so it might take a little time before it happens.

Not fudging the numbers: Let's say a user imports his fully downloaded torrent and wants to share it until ratio 1.5. However, since he will never download anything the all_time_download var will be 0. So the ratio will appear as MAX_RATIO+1 (aka 10000) which is bigger than 1.5. That means that he will never seed that torrent.

What I would expect form 1.5 ratio, is that the file(s) is shared to the amount of 1.5 times their size.
So on torrent import/create could the actual size of the files be used as the all_time_download start point ??

So on torrent import/create could the actual size of the files be used as the all_time_download start point ??

Yes, that is the current behavior of the code.

Here is a build of qBittorrent 3.2.0alpha sha1 78d4258 from git master with:
boost 1.57
libtorrent 1.0.3svn+r10582
qt: 4.8.6

Built using gcc 4.9.0.

Git changelog from last alpha: https://github.com/qbittorrent/qBittorr ... fffb99f7be


http://builds.shiki.hu/qbittorrent_3.2. ... _setup.exe

(sorry I didn't have time for a boost 1.55 build)

Automatic download & install. Thanks sledge.

Here is a build of qBittorrent 3.2.0alpha sha1 ca2dc325 from git master with:
boost 1.55
libtorrent 1.0.3svn+r10642
qt: 4.8.6

Built using gcc 4.9.0.

Git changelog from last alpha: https://github.com/qbittorrent/qBittorr ... eb99401e00


http://builds.shiki.hu/qbittorrent_3.2. ... _setup.exe

Downloading, installing, updating my signature, using & testing.

Thanks sledge.

I haven't tried the alpha's for a long while and I just moved from 3.1.11 to 3.2.0alpha_20141229_ca2dc325...
I get a few times more nodes for dht and a few times faster in d/l... What a great speed improvement!!! Thanks.

With the alpha, I highlighted ~200-300 torrents and right clicked. Program/ System freezed with high cpu usage. It's not happening with the stable version. With the stable version, the context menu appears in an instant. (xpsp3 x86)