On 2020-01-02 11:13, Radek wrote:
>> what about working directly on rsync side, specifying the maximum
>> transfer rate? (--bwlimit option)
> Setting the hard transfer rate/limit on the rsync side is not what I need. I want my boxes to be able to use whole available bandwidth anytime. I mean if other services need some bandwitdh they just get it with higher priority and my boxes always can use *the rest*. If there is a quiet it the network my boxes can use the whole highway.
>
> On Thu, 2 Jan 2020 17:57:19 +0100
> fRANz <andrea.francesconi@gmail.com> wrote:
>
>> On Thu, Jan 2, 2020 at 3:51 PM radek <rdk@int.pl> wrote:
>>
>>> I tried to do it by "catching" this traffic on [fw_rac]/[fw_krz] by specific rules [1] and setting the lowest priority fot it.
>>> Unfortunately it doesn't seem to work as expected. Bandwidth seems to be shared roughly equally with other traffic (tested with pushing data (netcat) through VPN in the same time).
>>> I would appreciate your advice or any clues on what I have done wrong. Thank you.
>> what about working directly on rsync side, specifying the maximum
>> transfer rate? (--bwlimit option)
>> -f
>>
>
FQ-CoDel may be useful for ensuring fair sharing of bandwidth. I use it
on some bandwidth constrained links and it works quite nicely at
ensuring that bandwidth is fairly distributed. I've found that adjusting
the quantum level to around 300 is nice for ensuring interactive
applications remain responsive/low latency, by prioritizing smaller
packets over larger bulk transfer packets.
No comments:
Post a Comment