<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hello,</div><div><br></div><div>You can have only one TCP/IP connection between node. </div><div>Yes, your idea of message collation is fine. There was even message post about this.</div><div><a href="http://www.ostinelli.net/boost-message-passing-between-erlang-nodes/">http://www.ostinelli.net/boost-message-passing-between-erlang-nodes/</a></div><div><br></div><div>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. </div><div><br></div><div>- Dmitry</div><br><div><div>On Jul 2, 2013, at 1:10 PM, Dror Mein <<a href="mailto:drormein@yahoo.com">drormein@yahoo.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><div style="background-color: rgb(255, 255, 255); font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; "><div><span>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?</span></div><div><br></div> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font size="2" face="Arial"> <b><span style="font-weight:bold;">From:</span></b> Jesper Louis Andersen <<a href="mailto:jesper.louis.andersen@erlang-solutions.com">jesper.louis.andersen@erlang-solutions.com</a>><br> <b><span style="font-weight: bold;">To:</span></b> Dror Mein <<a href="mailto:drormein@yahoo.com">drormein@yahoo.com</a>> <br><b><span style="font-weight:
bold;">Cc:</span></b> Gleb Peregud <<a href="mailto:gleber.p@gmail.com">gleber.p@gmail.com</a>>; Erlang-Questions Questions <<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>> <br> <b><span style="font-weight: bold;">Sent:</span></b> Tuesday, July 2, 2013 12:13 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [erlang-questions] Is there a lomit on erlang vm nodes connection speed<br> </font> </div> <div class="y_msg_container"><br>
<meta http-equiv="x-dns-prefetch-control" content="off"><div id="yiv1510216935"><div dir="ltr"><div class="yiv1510216935gmail_extra"><br><div class="yiv1510216935gmail_quote">On Tue, Jul 2, 2013 at 9:20 AM, Dror Mein <span dir="ltr"><<a rel="nofollow" ymailto="mailto:drormein@yahoo.com" target="_blank" href="mailto:drormein@yahoo.com">drormein@yahoo.com</a>></span> wrote:<br>
<blockquote class="yiv1510216935gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">From shell:</blockquote></div><br>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.</div>
<div class="yiv1510216935gmail_extra"><br></div><div class="yiv1510216935gmail_extra" style=""><br></div></div>
</div><meta http-equiv="x-dns-prefetch-control" content="on"><br><br></div> </div> </div> </div></div>_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>http://erlang.org/mailman/listinfo/erlang-questions<br></blockquote></div><br></body></html>