With that many destinations, a single JVM will have a lot of context switching to do. It may be best to partition your destinations across a cluster. Having said that, to scale up the number of destinations, memory will be your main requirement. Follow the advice from http://activemq.apache.org/javalangoutofmemory.html , and use the KahaDB store to reduce fd usage. How many concurrent connections do you expect? Scaling connections will require the use of NIO. There is an activemq-scaleability.xml configuration file in 5.3.0 that can provide a good starting point configuration.
2009/11/18 Igor Katkov <ikat...@gmail.com> > > Hi, > > Is it a good idea to create 500ooo+ queues and send messages to these > destinations? Load is a few messages per _minute_ into each queue. > Producers and consumers will be on different hosts. Network of brokers > topology. > > Does anyone have experience pushing ActiveMQ that far, or even further with > 2M queues and several messages a second? > > Will it scale to that extent? I can add boxes to host additional producers > and consumers, but not sure if pushing metadata of that mighty number of > queues around will be handled OK > -- > View this message in context: > http://old.nabble.com/500ooo%2B-queues--tp26417356p26417356.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
