I suggest you go for the one-destination-per-chatter model, and perhaps enable automatic deletion of inactive destinations to control the use of resources in an elastic manner.
Look at http://activemq.apache.org/delete-inactive-destinations.html. Hope that helps. Regards, *Raúl Kripalani* Principal Consultant | FuseSource Corp. r...@fusesource.com | fusesource.com <http://www.fusesource.com/> skype: raul.fuse | twitter: @raulvk <http://twitter.com/raulvk>, @fusenews<http://twitter.com/fusenews> blog: F3 - Flashes From the Field<http://blog.raulkr.net/?utm_source=fusesourceemail&utm_medium=email&utm_campaign=fusesourcemail> <http://twitter.com/fusenews> On 5 June 2012 06:25, Shine <activ...@club.webhop.org> wrote: > Hi, > > thanks for your response. > > There will be ~250 clients and all clients are almost connected at the same > time. All messages expire after 150 seconds. > > best regard > Shine > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Performance-queues-topics-vs-selectors-tp4652915p4652971.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
