|Re: [eclipse-incubator-e4-dev] Interesting article on modelling with prototype-based leanings|
Hi Paul,I think that Eclipse just after startup is not very bloated.It did some quick analysis of the heap usage (not classes)some time ago:and Eclipse would consume 22,7 Mbyte just after startup. If you count that there would be some easy ways to reduce the memory usage (see link above)I would not consider Eclipse to be bloated. At least not more bloated than Netbeans http://kohlerm.blogspot.com/2008/05/memory-consumption-of-netbeans-versus.html :]I did not look at the memory consumption of classes yet, because this information is not available from the heap dump, but I would assume that the amount of code already loaded would not be very large.My approach would therefore be to get as many plugins loaded as possible and then use JVM statistics to get the real footprint of the classes (in memory).My naive idea was that I just could maybe through some option turn off lazy loading. Otherwise I would have to click around in Eclipse to get the plugins loaded which seems to me would not be a very elegant approach.Regards,MarkusOn Wed, Oct 22, 2008 at 6:49 PM, Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx> wrote:
There's no "load everything" flag, but you could write a little plugin
to do it yourself by starting all INSTALLED bundles.
See org.osgi.framework.BundleContext.getBundles() and org.osgi.framework.Bundle
Do you have a specific use in mind? I don't think you would get the
desired results using the above method :-)
In OSGi it's more common to specify all the bundles you want to start
in the osgi.bundles property, though.
Hi floor. Make me a sammich! - GIR
eclipse-incubator-e4-dev mailing list
Back to the top