Bug in allocating upload bandwidth

[TheDude]

Hi !

[uPDATE: This was with Version 1.3, build 364. The same problem exists with Version 1.32 Beta build 395 - BUT the effect of the bug is less in quantity.]

1.3 is very good so far, BUT I found this one bug. Not totally obscure, but will only occur like a small percentage of the time.

I was downloading a torrent, and I wanted to start a new torrent to upload to everyone.

I didn't want my download to affect the uploading of the new torrent, so I limited the upload speed on the downloading torrent to only a fraction of my bandwidth. (I figured that it would download pretty slow, but any progress was better than none, and I would remove the limitation once I had seeded the new torrent fully.)

Then I started seeding the new torrent. However, the total upload speed was well below my stated and set upload speed. I did a bandwidth/speed check at a reliable site and it reported that I had most of my upload still available and unused.

All of the people I was uploading to, were getting exactly the same speed precisely.

Then, on a hunch, I set the downloading torrent to "Bandwidth Allocation -> Low" and the uploading new torrent to "Bandwidth Allocation -> High".

As soon as I did that, the upload on the uploading/seeding torrent jumped up and started using all the available bandwidth.

SO, the bug is that when an individual torrent has its Max Upload Bandwidth set, that setting is being ignored - in some cases - when the upload bandwidth is being allocated between torrents.

[Switeck]

Let me see if I understand this:

Say you had 1 downloading torrent and 1 seeding torrent, both uploading at 20 KB/sec.

And you limited the downloading torrent's upload speed to 10 KB/sec.

You're saying the seeding torrent remains at 20 KB/sec instead of increasing to 30 KB/sec?

[sentinel30]

I have just discovered an interesting bug. It seems to be on the same lines as the above posted topic.

In preferences I have global upload and download set to maximum.

I also have it set that when a torrent reaches 200% it reduces the upload speed to 3/kbs.

In Scheduler I have limited the upload speed to 10kb/s.

I have 2 torrents seeding and I double clicked both. (at the moment the scheduler is on limited)

The 1st one has reached the 200% and is running at 3kb/s - as it should be.

The 2nd one hasnt yet reached 200%, so should be set to zero(?), even with the sheduler limiter.

However it is set to 2kb/s!

I disabled the scheduler to see what would happen.

And both remained at their individual max upload speeds.

Is there another setting in preferences that I have missed?

I had to manually change it to zero.

Also at no point have I manually gone in and changed these numbers... (before resetting it to zero)

I have no need to change the individual upload speeds.

Thanks in advance

[TheDude]

Let me see if I understand this:

Say you had 1 downloading torrent and 1 seeding torrent, both uploading at 20 KB/sec.

And you limited the downloading torrent's upload speed to 10 KB/sec.

You're saying the seeding torrent remains at 20 KB/sec instead of increasing to 30 KB/sec?

No, the downloading torrent was limited before I added the seeding torrent.

As a result, the seeding torrent does not use the available upload bandwidth.

PS To Sentinel - no scheduler is involved in the bug I encountered, so you should start a separate thread - it only confuses the issues to combine them in one thread.