Hi In relation to why the POJO version is faster than the Camel route is that the POJO is all done in a single bean. When you route with Camel it adds additional processing in between for cross cutting concerns such as - error handling - stream cache - jmx instrumentation - copying messages changes from one node to the next
All together it cost performance. In Camel 2.0 we have paved the road to allow us to do speed optimizations under the cover without affecting the end user and being able to get on pair speed with Camel routing vs. more direct usage such as the POJO model. We have not yet focused too much on performance in Camel 1.x. This is a goal with the 2.x version to optimize speed and memory usage etc. The FUSE field team is excellent in getting great speed with AMQ, SMX and Camel together. I know they can get more than 1000 msg/sec with Camel in SMX between AMQ so its possible, on a regular PC. And that is on Camel 1.x We have a wiki page with ideas for speed optimizations in Camel 2.x http://camel.apache.org/camel-2x-speed-optimizations.html On Tue, Jul 28, 2009 at 6:39 PM, boday<[email protected]> wrote: > > I have tried setting maxMessagesPerTask=-1, concurrentConsumers=20, > maxConcurrentConsumers=20, but I'm still not getting any better throughput. > Any other ideas? > > Also, I can't find Camel 1.6.2 anywhere in the Maven repositories, it > doesn't appear to have been released yet. Also, any updates on when Camel > 2.0 will be available for use with SMX 3.3? I've read about many > performance improvements that I'd like to be able to take advantage of. > > thanks again... > > > > ----- > Ben - Senior Consultant > > -- > View this message in context: > http://www.nabble.com/Camel-throughput-issues...HTTP-to-AMQ-tp24648117p24703317.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
