Installing subsystem with large number of constituents takes forever or gives out of memory

Installing a large subsystem that contains a lot of bundles can cause the resolution phase to run for hours and sometimes causes out of memory, even with a feature subsystem.

I think this is caused by the fact that all the bundles inside the subsystem are attempted to be resolved in one shot. When you have 200+ bundles that gives an enormous resolution problem space.

In a plain OSGi framework such a scenario can be helped by installing bundles in stages, making life easier for the resolver.

Maybe subsystems can support this too. We could use the 'start-order' directive on the Subsystem-Content header to guide resolution and only resolve bundles on the current start-order as we progress through those.