Hi, Depends on how much services you have, but iPOJO has an internal event dispatcher improving startup time. The behavior is quite simple. When enabled, iPOJO registers only one service listener and dispatches events to the instances directly. So for the framework, it dispatches the events to only one service listener. The iPOJO internal dispatching can rely on the structure of iPOJO service dependencies.
The benefits of such mechanism are visible only for big configurations dealing with an event storm when they start. Notice also that iPOJO, as SCR and Blueprint, is an 'extender' and thus analyzes bundles when they are starting. This introduce an overhead. Regards, Clement On 11 oct. 2013, at 12:47, Roland <[email protected]> wrote: > Hi all! > Has anyone ever tested how fast Apache Felix starts with iPOJO, SCR or > classic (BundleActivator)? I think the latter is faster. > > Regards? > Roland > > > > -- > View this message in context: > http://apache-felix.18485.x6.nabble.com/How-to-improve-the-start-time-of-Apache-Felix-tp5004833p5005501.html > Sent from the Apache Felix - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
