#5 Configurable bandwidth and connect limits

[Adam Davis]

Before I can deploy this system on a company server I'd
have to be able to limit the bandwidth consumed for
backup processes and/or limit them by time and day. It
would also be good to limit the number of connections
accepted from peers at once.

I'm looking at other options, but using an external
rate limiting or traffic shaping solution provides
another point of failure and additional setup and
maintenance. I suspect that this problem would be
better solved inside DIBS - more control over what is
backed up during rate limited time. It can also
provide statistics about how long backups are taking
and perhaps even raise and lower its own rate so that
throughout the day it stays close to an average rate,
rather than being bursty.

To start it may be easiest to make it a simple static
setting that can be updated while the program is
running so cron can change it, something like
dibs -setbw 100k

I would suggest using bits per second, with k, m, g as
postfixes to denote kilo, mega, or giga as needed, but
whatever is convenient will be fine.

-Adam

[Emin Martinian]

Logged In: YES
user_id=665772

Thank you for the suggestion. I agree that some kind of
bandwidth monitoring/shaping is a good idea and would be
best implemented in DIBS as opposed to an external program.
I'll put this near the top of the list of things to do.

-Emin