[rabbitmq-discuss] High Performance Setup Strategy

Mon Feb 18 10:53:07 GMT 2013

Good morning,

I'm a little bit curious about the setup strategy of a project. Maybe 
someone of you can make it clear.

Situation: 
Community Website, running on several php-nodes.

Destination:
Implementation of Websockets with nodejs.

Attempts:
One big Server (24 Cores) running Rabbitmq, every websocket-worker connects 
to this one.
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)
3 Websocket-Hosts, each running 16 Node-Worker. (16 Cores/Server)

Every websocket-worker creates an own queue.
There are 100 exchanges, the users are being sorted in there by their 
UserID. Exchange-Type: direct.
(Using only one exchange crashes when reaching 64k bindings)

Problem:
Queues are starting to fill up when reaching 120k Bindings (130-140k unique 
Websocket-Connections). 4-6k delivered Msg/s.
Load: 
Big one (18-20 / 24)
php-nodes (6 / 16)
Nodejs-Hosts (5 / 16)

I want to know your opinion about this setup, or tips to build a better one.

We want to serve 300-500k Connections at any time with at least hardware as 
possible.

Greetings,
Florian

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130218/f8a97056/attachment.htm>