Yes Claus, thread safety out of the box would be nice. We spent last week digging into some massive performance regression with Camel & Ruby and parallel processing: when processing 200 messages in parallel (5 concurrent consumers) - memory consumption increased from 30MB (Camel 2.8.0) to 90MB (2.12.0) to 1100MB (!) (2.14.0) - processing time increased from 2s (2.8.0) to 4s (2.12.0) to 78s (!) (2.14.0)
I uploaded a maven project with the different version setups: camel-ruby.zip <http://camel.465427.n5.nabble.com/file/n5760324/camel-ruby.zip> Any ideas what is causing this performance setback in the higher Camel versions? Claus Ibsen-2 wrote > So ideally camel-ruby should set that JVM system property if not > already set? so you get the thread safe out of the box? -- View this message in context: http://camel.465427.n5.nabble.com/NPE-with-language-ruby-and-concurrentConsumers-tp5759703p5760324.html Sent from the Camel - Users mailing list archive at Nabble.com.
