GS.Chandra N wrote:
On Tue, Feb 10, 2009 at 6:57 PM, Carl Trieloff <[email protected]>wrote:
either way it should be fine for the broker. the topic exchange is the
least efficient match so I
would test performance for your case if you plan to bind 80,000 binding to
it
Thanks for the reply Carl.
The routing model is what i'm trying to evaluate for perf testing, as we
really cant have all the clients recieving all the broadcasts, as the
traffic would then become prohibitively high. Compression is something we
are looking at adding on top of this for select connections which come
through really thin channels to further reduce the bandwidth requirements.
Are there any limits / best practises / known issues around how to achieve
this type of a setup (many clients + many subscriptions) in as performant a
manner as possible?
Thanks
gs
Note that if a single incoming messages is sent to multiple queues bound to an
exchange that does *not* mean a physical copy per queue of message data in
broker memory. Each queue just holds a pointer to reference counted message
data. So having many clients bind private queues to a single exchange should be
a reasonably efficient way to broadcast messages.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
