Acca .net vs Orleans

Question

Hi, I am in the early stage of choosing an actor structure for the project that I am about to start. As far as I know, Orleans was supposed to help the developer as much pain as possible, at the cost of some performance. At Akka.net, I know that the size of an actor is 400 bytes. If I'm right, and you need to go low to handle cluster connections and things managed with orleans, but will bring you great performance.

The only performance metrics I found online for Orleans :

Use of X-Large virtual machines (8 processor cores / RAM 14 GB) on Microsoft Azure with one bin for each virtual machine:

Mirrors process no more than 1000 requests per second. The silo will handle a maximum of 10,000 requests per second. The silo will contain 100,000 active grains.

And for Akka.net in the main page :

50 million msg / sec on one machine. Small amount of memory; ~ 2.5 million members per GB heap.

I would like to know which machines were used in the Akka.net script and how they execute Grain vs Actor (in terms of requests per second and the number of grains / actors you can fit more or less in GB of RAM) and how much grain weight is in memory.

With quotes from Orleans and Akka.net, it seems that Akka.net works much better, but I would like to get a further comparison both in terms of performance.

I found this Akka.Net VS MS Orleans Comparison and Orleans and Akka Actors: A Comparison , but does not address the issue of performance.

Thanks!

Answer 1

Akka.net reports local messages, which are mainly function calls. Orleans reports deleted messages, see RPC. This is the main difference. Of course, there are other differences.

In addition to the above, the only real advice I can give you is to measure yourself, for your realistic test, in a setting that will be as close to production as possible in terms of communication pattern and number of servers.