Feedback for Test 17 (internal testing)

[DavidMc0]

@whiteoutmashups

Could someone please explain what the rate limiter is, and why we’re adding IP’s back into SAFE?

The rate limiter was introduced in the June 22nd update:

@maidsafe

We start with defining what is the total bandwidth that can be handled non-disruptively by the network on behalf of the clients (bandwidth usage due to churn/data-relocation etc. are over and above this). These numbers will likely be tweaked based on test results and actual network capability. Then we divide that by the total number of potential proxies we plan the testnet for, thus getting the maximum throughput allowed for clients per proxy. Then, depending on the total number of connected clients, we distribute this bandwidth evenly among them for fair usage policy. The Rate Limiter ensures that no client goes above the maximum throughput it is allowed (throttling). There is an upper cap of 10 clients per proxy.

As I understand it, this is to make sure that if a client is using too much bandwidth to the detriment of the network / other clients, they are throttled. Some kind of mechanism will be needed to ensure nobody can disrupt the network by overloading it with download requests etc. Any resource that is free is a potential attack point unless there’s some other rationing mechanism. I believe a rationing mechanism for a ‘free’ resource the network provides to clients.

Please correct me if I’ve got this all wrong

IP addresses are needed for white listing users for early tests to ensure the network isn’t disrupted again like it was in previous public tests. This serves a temporary purpose for this private testing stage.

Again, if I’ve got this wrong, someone with a better understanding can correct me!