As I recall, the distributed pub/sub sends a single message to each node,
then the message is distributed to the subscribers on those nodes. So it's
likely more efficient to use this method to ask the actors for their state.
More efficient both ways -- no million-iteration loop to generate the
Just one addition to that: have you chosen a better-than-default
serializer? I generally agree with the principle of "no premature
optimization", but this *is* a common newbie problem, and might make a
major difference in the case you're describing.
That is, it's generally agreed that the
Fair comment. :)
On Wednesday, June 8, 2016 at 11:25:22 AM UTC-5, Ryan Tanner wrote:
>
> Unless you've profiled and found it to be a problem, worry about it later.
>
> On Wednesday, June 8, 2016 at 10:10:37 AM UTC-6, kraythe wrote:
>>
>> Sorry but i have another newbie question. I have an actor
Unless you've profiled and found it to be a problem, worry about it later.
On Wednesday, June 8, 2016 at 10:10:37 AM UTC-6, kraythe wrote:
>
> Sorry but i have another newbie question. I have an actor that uses
> cluster sharding. There are potentially millions of these in the sytem
>
Sorry but i have another newbie question. I have an actor that uses cluster
sharding. There are potentially millions of these in the sytem concurrently
and they maintain some state. At some point I would like to contact a
million of these and ask them for their state to render information or
