Hello Florian,<div><br></div><div>Another way to achieve stable and high performance would be to install Solace Appliances. With them you can reach 200k concurrent connections per box and also get more than 230k messages/second fully guaranteed. You would have to replace AMQP with JMS though....</div><div><p class="MsoNormal"><span lang="EN-GB"><font color="#000000">2 Solace 3260 (needed for 200K connections with HA) would replace :<o:p></o:p></font></span></p>
<p class="MsoNormal"><span lang="EN-GB"><font color="#000000">1 server 24 cores<o:p></o:p></font></span></p>
<p class="MsoNormal"><span lang="EN-GB"><font color="#000000">3 servers 16 cores<o:p></o:p></font></span></p>
<p class="MsoNormal"><span lang="EN-GB"><font color="#000000">=120K connections<o:p></o:p></font></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p><font color="#000000"> </font></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><font color="#000000">for 480K connections:<o:p></o:p></font></span></p>
<p class="MsoNormal"><span lang="EN-GB"><font color="#000000">need at least 16 servers (4 24 cores and 12 16 cores).<o:p></o:p></font></span></p>
<p class="MsoNormal"><span lang="EN-GB"><font color="#000000">vs :<o:p></o:p></font></span></p>
<font color="#000000"><span lang="EN-GB" style="font-size: 11pt; font-family: Calibri, sans-serif;">6 solace appliances </span><br></font><div><font color="#000000"><br></font></div><div><font color="#000000">Cheers</font></div><div><font color="#000000">Daniel</font></div><div><font color="#000000"><br></font></div><div><font color="#000000"><br>Am Montag, 18. Februar 2013 11:53:07 UTC+1 schrieb Florian Müller:</font><blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><div><font color="#000000">Good morning,</font><br></div><div><br></div><div>I'm a little bit curious about the setup strategy of a project. Maybe someone of you can make it clear.</div><div><br></div><div>Situation: </div><div>Community Website, running on several php-nodes.</div><div><br></div><div>Destination:</div><div>Implementation of Websockets with nodejs.</div><div><br></div><div>Attempts:</div><div>One big Server (24 Cores) running Rabbitmq, every websocket-worker connects to this one.</div><div>Every php-node is running an own Rabbitmq, php connects to localhost using Amqp. Every kind of notifications is being sent to it, but only if the target user is actually connected to one socket (Solved per memcache-entry)</div><div>3 Websocket-Hosts, each running 16 Node-Worker. (16 Cores/Server)</div><div><br></div><div>Every websocket-worker creates an own queue.</div><div>There are 100 exchanges, the users are being sorted in there by their UserID. Exchange-Type: direct.</div><div>(Using only one exchange crashes when reaching 64k bindings)</div><div><br></div><div>Problem:</div><div>Queues are starting to fill up when reaching 120k Bindings (130-140k unique Websocket-Connections). 4-6k delivered Msg/s.</div><div>Load: </div><div>Big one (18-20 / 24)</div><div>php-nodes (6 / 16)</div><div>Nodejs-Hosts (5 / 16)</div><div><br></div><div>I want to know your opinion about this setup, or tips to build a better one.</div><div><br></div><div>We want to serve 300-500k Connections at any time with at least hardware as possible.</div><div><br></div><div>Greetings,</div><div>Florian</div><div><br></div><div><br></div></blockquote></div></div>