-
-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remote performance - 2.9 mil msg/sec #50
Comments
Good work @rogeralsing & contributors! |
Very nice work indeed @rogeralsing + contributors! May I ask what the hardware specs are needed to achieve these numbers? |
@frankbolero These benchmarks are on a modern dev laptop with a Xeon E3-1505M@2.80GHz. I don't think RAM and disk should matter much. Would be nice to do some real benchmarks on actual server hardware :) |
Is the benchmarking included in the sln? I have a Xeon E5-4607 based server(long live ebay) which i could use to benchmark. |
@mastorm Yes they are all in the "examples" folder. |
@mastorm the different benchmarks we have are:
It should be noted that the numbers for remote are on loopback, which makes it somewhat nonsense. |
The tests should be run with release mode and with server GC enabled (settings included in projects) |
@mastorm Have you had time to run any benchmarks on an actual server? Would be interesting to see how it performs :) |
For anyone interested in this topic, the current numbers are 2.9 mil msg/sec for .NET |
As of yesterday, Remote performance in Proto.Actor .NET is now slightly better than the Go counterpart.
2.5+ million messages per sec in .NET
vs
2.4+ million messages per sec in Go
Which puts us on par with ZeroMQ.
This can be seen in contrast to the performance of Akka NET
akkadotnet/akka.net#2378 (comment)
We are now more than 50 times faster over the network, with version tolerant serialization and cross platform communication.
The text was updated successfully, but these errors were encountered: