On Thu, Jun 28, 2012 at 6:26 PM, Edwin <edwin.rabbi...@gmail.com> wrote: > Thanks for the responses Claus, Henryk > > I understand that each seda queue consumer will have its own thread pool. > However, my concern more relates to the footprint imposed on the JVM by > creating 1000+ SEDA Queues. > > Sounds like you echo my concerns Henryk. Was wondering if there is any kind > of metrics on the overhead of SEDA queues. I have concerns similar to those > outlined by Henryk >
A SEDA queue is a pure in memory queue using the BlockingQueue API from the JDK. You can easily create 1000 of these SEDA queues. Its only when you either or do both - add a lot of messages to these queues, eg adding messages faster than you can consume (taking up memory) - has 1000 consumers running at the same time, as that is at least 1000 threads in the JVM. > Thanks > Edwin > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Footprint-of-SEDA-queues-tp5715128p5715232.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
