Carl Camilleri

Thanks, in reply to: > > ASKing a local actor I get >111k req/s throughput, but ASKing a remote actor drops throughput to 2.4k req/s. > > The local actor...

Correct, basically the setup is as follows: instance-1 : Windows VM running an instance of the code in the repo instance-2 : Windows VM running an instance of the code...

Having done some checks I believe the perf. bottleneck is coming from the amount of boxing/unboxing that is performed by the `ShardMessageExtractor` The attached ZIP contains: patch_without-unboxing.diff - a patch...

@Aaronontheweb thanks for this information. First of all, apologies for the initial indication that boxing/unboxing was causing the issue - it was a red herring as indeed with your benchmark...

@to11mtm @Aaronontheweb thanks for the analysis in #5230 . Just to confirm do we expect this to improve performance even in the case of the following approach? :  ...

@to11mtm thanks, I have added a small benchmark as part of `ShardMessageRoutingBenchmarks` to test this approach with a RoundRobinPool of 50, and even increased to 1000. The results are below:...

@Aaronontheweb I understand it's not ideal to `await` however I'm not sure I understand what should be the correct approach for the use case at hand (https://github.com/akkadotnet/akka.net/issues/5203#issuecomment-903241323) ? In principle...

Hi, Just in case it is of interest, I have in the meantime performed similar benchmarks in the JVM world. I have reported my findings at https://github.com/akka/akka/issues/30546. Throughput is faster...