bt icon indicating copy to clipboard operation
bt copied to clipboard

Limitable download speed (and upload speed)

Open ThatLurker opened this issue 7 years ago • 3 comments

Don't think this need further explaining :P

ThatLurker avatar Aug 02 '17 23:08 ThatLurker

Should limit both applied on global and per client?

I just wonder that client(or task) specific network IO rate limitation is necessary or not

phillui-37 avatar Jan 16 '19 13:01 phillui-37

I'm personally not in favour of limiting speed per client, because with sufficiently large number of clients it may and will go out of control. Global rate limit (per runtime) is OK. I guess, request producers will have to check with some shared service, if there is any free bandwidth to create and enqueue a new piece request. Then, if the need arises, this shared service may be updated to act as a short-term buffer for new requests and prioritize actual sending of requests based on priorities of individual torrents (which, in effect, would be the same as per client limits.) But this is how I see it, so please feel free to share any suggestions/considerations :)

atomashpolskiy avatar Jan 16 '19 16:01 atomashpolskiy

I think your idea is good enough as this is common practice of bt apps

phillui-37 avatar Jan 16 '19 16:01 phillui-37