Hi
Current camel-seda component is based on the queue with a thread pool to
consume and produce the message. It's much like the SEDA that you found.
But after went through the whole story, the write had some theories
which made me think the research papers were doing the different things
as we do in camel.
camel-seda only has one queue, and it doesn't pull the message from the
network, so I don't think camel-seda has this kind of issue.
Willem
vcheruvu wrote:
Hi,
I came across site about SEDA implementation,
http://www.eecs.harvard.edu/~mdw/proj/seda/ . Does camel SEDA component
follow this model? If it does, author stated that "It is also worth noting
that a number of recent research papers have demonstrated that the SEDA
prototype (in Java) performs poorly compared to threaded or event-based
systems implemented in C....... Also, SEDA imposes a high context switch
overhead in certain cases, depending on the number of threads and stages
used, and the processing granularity within each stage. " Is this still a
concern with SEDA implementation in Camel?
Kind regards,
-Vid-
