Classes are loaded when they are first needed. This is the case for Java in general, not just OSGi.
If a bundle has no Bundle-Activator, then no classes will be loaded for the bundle as a result of starting. The framework can even defer the creation of a classloader for the bundle. Of course, some classes *may* be loaded very shortly after activation, for example due to Declarative Services or Blueprint declarations existing in that bundle. On Thu, Dec 5, 2013 at 10:50 AM, Daniel McGreal <[email protected]> wrote: > Also, what is the impact of starting a bundle? For example, are all its > classes loaded into memory at this time, or when they are first requested? > Best, Dan. > > On 5 Dec 2013, at 09:00, Daniel McGreal wrote: > > > Thanks. > > May I try a different question then? > > > > In Felix, is it known how memory requirements scale with OSGi > functionality such as: > > Quantity of bundles, > > Quantity of wires, > > Unused exported packages, > > SCR and its various settings, > > Anything else anyone can contribute, > > > > Best wishes, Dan. > > > > On 5 Dec 2013, at 08:22, Vadim <[email protected]> wrote: > > > >> I have such experience. Memory usage optimizations is application > specific. > >> > >> On 12/05/2013 12:07 PM, Daniel McGreal wrote: > >>> Dear Felix Users, > >>> > >>> I wonder if there is anyone with experience of optimising a Felix > application's memory usage. Are there any OSGi or Felix centric tips? > >>> > >>> Many thanks, > >>> Dan. > >>> --------------------------------------------------------------------- > >>> 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] > >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
