Community
Participate
Working Groups
The ConfigurationWrapper's constructor causes the LazyManipulator to activate when it looks for the OSGiInstallArea. On my laptop with the SDK installed this adds a fixed cost of 600ms in the prephase to initialize the manipulator and about 1200ms in the post phase to save the manipulator. This occurs whenever an OSGi bundle is involved even if no "manipulating is being done. For the default phaseset this adds a fixed cost of around 10s. For typical install/uninstall scenarios we should be able to reduce this by about 8s. We can defer the lookup of the OSGiInstallArea in the configuration wrapper and save the time when no "real" manipulation is done.
Created attachment 93750 [details] patch
I just did a little testing of this patch comparing a basic sdk install vs. an sdk with tptp install and found that this patch provides a "fixed" reduction of about 8s seemingly independent of the number of bundles installed.
Created attachment 93861 [details] replacement bundle for I20080327-0100
path released. marking fixed.