[erlang-questions] Amazon AWS benchmarking of erlang-diameter not upto the mark

Dmitry Kolesnikov dmkolesnikov@REDACTED
Mon Aug 29 21:04:54 CEST 2016


You’ve experienced difference due to network configuration. CPU factor is important but I’ll spent more time to study network config.

You have not defined to us your local network config, its latency, used operating system, networking kernel options and Erlang flags. Similarly, your AWS config is not know to us either. 

Best Regards, 

> On Aug 29, 2016, at 6:55 PM, Arshad Ansari <arshadansari27@REDACTED> wrote:
> Hello there,
> Today, as a part of evalution of erlang diameter client, relay & server, I was benchmarking for requests per second. This same test was performed by me on my local network and I was able to get 30K requests per second between client and server using a single connection. However, on Aws I got to only about 11-12K requests per second. I had used c3.x4large instance with 16 cores and 30 GB ram for both client and server, which is 4 times the core I have and twice the ram I had when I was testing locally. These are compute enhanced instances to make sure I get to use core to the maximum, but I wasn't even using 60% of cores on server and 80% of cores on client.  I even used the same placement group to get 10GBps network bandwidth. I can't think of any reason why there would be just a downgrade. Has anyone experienced something of this sort on Aws while benchmarking erlang?
> Thanks in advance for the help.
> Regards,
> Arshad
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

More information about the erlang-questions mailing list