[erlang-questions] Is there a lomit on erlang vm nodes connection speed

Dmitry Kolesnikov dmkolesnikov@REDACTED
Tue Jul 2 13:53:45 CEST 2013


You can have only one TCP/IP connection between node. 
Yes, your idea of message collation is fine. There was even message post about this.

I think you should split data and signalling to different channels, at least this is my approach. Use erlang distribution only for cluster coordination but use plain TCP/IP sockets for data path.   

- Dmitry

On Jul 2, 2013, at 1:10 PM, Dror Mein <drormein@REDACTED> wrote:

> You were right. increasing the message size to 10000 allowed me to reach 1-2Gbps. I guess the simple solution is to collate messages in a list and send them together. Is there another way you can think of? Can I configure the erlang vm to open more tcp connections between two nodes? will that solve the problem?
> From: Jesper Louis Andersen <jesper.louis.andersen@REDACTED>
> To: Dror Mein <drormein@REDACTED> 
> Cc: Gleb Peregud <gleber.p@REDACTED>; Erlang-Questions Questions <erlang-questions@REDACTED> 
> Sent: Tuesday, July 2, 2013 12:13 PM
> Subject: Re: [erlang-questions] Is there a lomit on erlang vm nodes connection speed
> On Tue, Jul 2, 2013 at 9:20 AM, Dror Mein <drormein@REDACTED> wrote:
> From shell:
> Note: The shell is interpreted and you are building a closure for no reason. Try pushing your code into a module and then compiling that module to bytecode and run it again. Chances are you are basically just being bitten by interpretation overhead. Also, you should probably increase the message size to around 100 bytes if that is what you expect to send and receive. There is a messaging overhead which you are paying as well.
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130702/b9ff5597/attachment.htm>

More information about the erlang-questions mailing list