t;> removed), OR one task per entity (dynamically added and removed), and a
>> single partition per task. Since all data is basically changed on each
>> access, and is stored in a central DB, we have no use for "replicas".
>>
>> Secondly, since the "size&q
r task. Since all data is basically changed on each
> access, and is stored in a central DB, we have no use for "replicas".
>
> Secondly, since the "size" of each entity can vary a lot, our LB takes the
> entity size into consideration (together with CPU load and a f
all data is basically changed on each access, and is stored in a
central DB, we have no use for "replicas".
Secondly, since the "size" of each entity can vary a lot, our LB takes the
entity size into consideration (together with CPU load and a few other factors)
when
