Bandwidth handling problem 24682q

[crypticus]

It seems there are still problems about order and bandwidth handling...

Check this out, my 5MB speed NOT even accessed by FDM let alone shared correctly, when there are different priorities set.


5MB bandwidth is accessed by FDM if all priorities are set equal. But then there won't be any simultaneous s. So FDM is not checking my maximum bandwidth and sharing it among s.


For me it is a big problem for a software that says " manager" in its title. Since it is not managing anything. Only thing FDM is capable is to something. also i sent pull request for language translation update but it seems no one cares its been months... total joke.

[Alex]

Hello,
It tries to keep bandwidth free in a hope that the green will be able to utilize it at some time.
However, in case this does not happen during a reasonable period of time, it should also let the other less prioritized s to use more bandwidth. If it does not happen, it could be a bug. We'll check it.

I don't see any pending pull requests. Please make sure it's not an issue on your side. The repository is located here: https://github.com/FreeManagerT ... calization.

[Alex]

Could you please post here a screenshot with your Traffic Limits settings?

[Alex]

It seems there are still problems about order and bandwidth handling...

There is no issue with order handling on your screenshots. FDM always s in the order s were added. Except the case when the has enabled -defined order and changes it using arrows.
Your s list is sorted by name, so you can't see the actual order of ing. Sort it by date added (or custom order) to see the actual order of ing.

[crypticus]

So you think thi sis normal?

super store can be ed with 4-5mb speed when its prioritized. but when it is not priotized its not even ed properly even tho there is available bandwith. If you think this is normal then it's time to switch back to idm. Its so dumb that i have to discuss this problem with you. a manager cannot properly adjust speeds when there are available bandwith.

[Alex]

Hello,

So you think thi sis normal?

I've already told you that this can be a bug and we'll check it. But yes, this is normal during some period of time (I don't , maybe 30-60 seconds). It's by design.

However, it's a torrent. It depends on available peers. You can on a full speed and stop ing at all in a few seconds if a single peer leaves (for example), or the ing speed can drop dramatically at any time. Regardless of the torrent's priority.
You can expect a reliable ing speed only in case there are enough active seeds on this torrent. This means, also, that you can still have bad speeds even in case you have, for example, dozens of seeds and hundreds or even thousands of leeches.

25 for maximum total number of connections is a way too low for torrents. You are just choking your torrent s by such a config.

[Alex]

P.S. Your config is a joke What's the point to have 25 connections limit for 15 (!) s?? Thus, you allow 25/15=~1.7 connections per . How can you expect any reasonable speeds with such a config? This config is inappropriate even for non-torrent s.

[Alex]

P.P.S. On your screenshots, the number of active s is 2-3. Still, 25/3 or even 25/2 is a way too low for torrents. This can be a kind of appropriate for regular s btw.

[crypticus]

Totally irrevelant in this case... not surprised to your answer.

[Alex]

Hello,
This one should be better in the next update. Please check it and let us know about your experience