It looks like this behavior changed in Camel 2.2. I noticed it when switching my camel-jmx component from 2.1 to 2.5-SNAPSHOT. Suddenly my suite of unit tests went from 1 second to 6 seconds. I can recreate this behavior with versions 2.2, 2.3, and 2.5-SNAPSHOT. I didn't try with 2.4.
The initial load time is below a second as you've indicated but it's still undesirable in certain cases. I'll run a couple of additional tests and enter a JIRA ticket. On Mon, Oct 18, 2010 at 11:31 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Mon, Oct 18, 2010 at 5:24 PM, abentley <abent...@ll.mit.edu> wrote: >> >> -1 >> The CamelContext init is very slow now. It seems to load every type >> converter upon startup. We create , start, stop, delete endpoints (routes) >> dynamically, increased start-up lag of each context is now very noticeable. >> Could the type converters be "lazy loaded" ? I understand if you want to >> push this off to 3.0. my 2 cents. > > It logs how long time it take to load the type converters. Check your logs. > It ought to do that in < 1 sec. > > Create a ticket in JIRA if you are looking for an option to disable > loading type converters on startup. > > >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-5-0-tp3216830p3217639.html >> Sent from the Camel Development mailing list archive at Nabble.com. >> > > > > -- > Claus Ibsen > Apache Camel Committer > > Author of Camel in Action: http://www.manning.com/ibsen/ > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus >
