Alternate upload rate when not downloading in scheduler

[kurahashi]

Right now it's available in global network settings only - I hope it wouldn't be a big problem to add this feature to scheduler?

[ColdArmor]

Yeah I would like to see that also and it would be relatively simple to add it there.

[Keloran]

1.1.8

Network Options -> Alternative upload rate when not downloading

[silverfire]

Yeah I've been using that feature a lot in the 1.1.8 beta builds. I cap my upload at 75KB/s while I'm downloading, but I expand that to 1MB/s when I'm done, and since I'm already connected to a bunch of clients, when that 1MB/s lets loose, I go up to my 200% pretty quickly

[kurahashi]

1.1.8

Network Options -> Alternative upload rate when not downloading

I don't know about 1.1.8, but in the latest official 1.1.7.2 this option is not available for scheduler.

But leaving this aside - I think there could be better solution.

As we know, the reason why we are using alternative upload limits when downloading or not is the overhead, created by the downloads and thus consuming our precious upstream (especially in asymetric connections) - what may lead to whole connection chocking.

BUT. The overhead varies greatly, and is - more or less - linear to the number of torrents we are downloading. For example when we are downloading only one torrent (and only seeding rest) the overhead is quite small. Contrary, when we are downloading four torrents together, the overhead is much bigger. Finally, when we are only seeding it is practically zero.

So how about option which would allow us to allocate defined by us overhead space per every torrent we are downloading?

Example:

let's assume we have 32kB/s (256kb/s) upstream.

We are setting global max upload rate to 30kB/s.

Now, we are setting overhead alocation for 2kB/s per every torrent we are downloading.

Then uTorrent will automatically adjust our global upload rate depending of the number of torrents we are downloading. Using above settings would it be 28kB/s for 1 torrent, 26kB/s for two torrents, etc... and 30kB/s for zero torrents (the number of torrents we are seedings doesn't matter). Note - in this particular case (only seeding) it would be working as the current alternate upload limit.

This option should also work with the scheduler without any problems - scheduler would only adjust begining max upload rate, overhead allocation rates would be left intact.