I’m in the process of writing an RFC for managing bandwidth consumption of vaults.
It would be useful to get some input from the community before it’s submitted for review.
Bandwidth settings are very important for vaults, since many users have bandwidth caps and hitting that cap results in an extremely negative experience of slow internet, possibly for several weeks. Even without caps, having the entire connection consumed in bursts can significantly disrupt other activities.
In my experience with coin farming/mining, users simply want to get started asap and sometimes don’t do enough research, especially when getting started is easy. Without a bandwidth cap setting, new farmers will get stung by running a vault and maxing out their bandwidth. This could result in unnecessary negativity toward safe, similar to the negativity experienced in bitcoin when users were stung by wallets lacking encryption.
There are a couple of configuration options required:
- maximum instantaneous bandwidth so it doesn’t consume the whole connection (needs individual up and down settings)
- total monthly (or weekly etc) consumption according to the plan and usage by non-vault resources.
But there’s a catch to bandwidth settings related to vault ranking. If bandwidth limits are reached, the vault appears unavailable (and effectively is unavailable, albeit temporarily). How should this be treated in the vault ranking algorithm? Should it have the effect of the vault being offline, or should it have some other in-between effect?
This is a tricky bit of configuration to design, but I feel it to be essential. Looking forward to hearing your thoughts on this topic.
Some relevant reading: