Managing thousands of Actors with frequent, small updates

[ChristianDoh-while]

Hi!

While searching for an alternative architecture, I recently came across the actor model and pekko. This raises the question of how pekko can be used to achieve high performance.

Consider the following:

• 1,000 to 10,000 long-lived actors are expected
• Updates (for each actor!) arrive every 5 seconds
• The updates themselves are small (maximum of 10 primitives)

Is this information sufficient to roughly determine whether pekko could quickly become a bottleneck in this case?

Thanks in advance!

[mdedetrich]

Just going on the information provided, this is well within means for pekko actors. There are akka/pekko systems out there with millions of actors on commodity systems as actors are extremely cheap (thats one of the core points of them). I remember reading somewhere that many-million actor systems only uses around 1 gb of heap.

[He-Pin]

https://github.com/arktwin/arktwin is using Pekko