[EnMasse] AddressController performance / ConfigMap lookups

[Gordon Sim]

On 13/03/18 09:16, Ulf Lilleengen wrote:
> If one address status needs to be changed, the controller then have to 
> read/write 1000 addresses worth of data, so I wouldn't say that it is 
> more manageable. If the problem is that the kubernetes master is 
> overloaded by enmasse use, this could even make it worse.

It is certainly speculative, but often smaller numbers of slightly 
larger data items are easier to manage and cause less load. While 
updating status would indeed cause some unneeded data transfer, 
retrieval of the addresses (which I would argue is by far the more 
common operation, assuming the addresses change relatively infrequently 
on a running system) would involve far fewer calls. Likewise for a bulk 
update of addresses (10,000 PUTs will generally cause more load that 10, 
even if the latter have more data in them).

In any case though, I would suggest we start with some actual 
experiments on pushing the scale wrt the number of addresses and find 
out where the actual bottlenecks are and figure out how to alleviate them.