On Tue, Jul 28, 2009 at 8:56 PM, boday<[email protected]> wrote: > > Thanks for the information. This definitely makes me hesitant to continue > using Camel 1.6.X with SMX 3.X. It sounds like there are various > performance issues that likely won't be resolved until I move to 2.X and SMX > 4 (neither of which is released yet). Any ETA on when both SMX 4 and Camel > 2.0 will be production ready? > In september 2009 FUSE ESB 4.2 is planned to be released that is based on SMX 4 and Camel 2.
> I guess I'm back to using servicemix-eip, servicemix-jms and servicemix-http > components (painful in comparison to the Camel implementation). > > From a performance perspective. I am seeing decent numbers routing from > HTTP to AMQ now (500+/sec), but as soon as I route through in either a > process() method or a JBI service, the throughput drops significantly > (~100/sec). I'm going to rework my application to not use Camel at all to > see where I end up. You should disable error handling and JMX (might not give as much) to get better performance. In the Java DSL errorHandler(noErrorHandler); > > Anyone else have any comments on this? Are others seeing better performance > using these components? > > thanks... > > > > > ----- > Ben - Senior Consultant > > -- > View this message in context: > http://www.nabble.com/Camel-throughput-issues...HTTP-to-AMQ-tp24648117p24705812.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
