On Tue, Jun 26, 2012 at 7:09 PM, Edwin <edwin.rabbi...@gmail.com> wrote:
> Hi Folks,
>
> I have a route which takes larges volumes of messages from an
> endpoint(custom), splits the message in to subsets of messages via the load
> balancer EIP and places on 5 different SEDA queues.
>
> I have 200 of these routes:
> from("custom:endpoint?param1=session1").loadBalance()....to("seda:session1_1","seda:session1_2",..."seda:session15")
> .......
> .......
> from("custom:endpoint?param1=session200").loadBalance()....to("seda:session200_1","seda:session200_2",..."seda:session2_200")
>
> Consequently, I now have potentially in excess of 1000 SEDA queues. Just
> wondering what kind of footprint this number of SEDA queues have in terms of
> performance and memory?
>
> Would folks have concerns with this number of SEDA queues?
>No, as each consumer from a seda queue has its own thread pool / threads, which mean you will have 1000+ threads to consume from the seda queues, if you have all queues in use at the same time. > Thanks, > Edwin > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Footprint-of-SEDA-queues-tp5715128.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
