Bug 90350 - Explore simple OSGi state optimizations in maintenance branch
Summary: Explore simple OSGi state optimizations in maintenance branch
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2005-04-05 15:07 EDT by John Arthorne CLA
Modified: 2005-09-28 10:18 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2005-04-05 15:07:20 EDT 
Build: 3.0.2

Great improvements have been made to the OSGI memory characteristics in the 3.1
stream.  We should consider back-porting some of these fixes, or else come up
with simpler fixes in the 3.0.2 stream, to help products that are built on our
maintenance releases.

For example, interning the bundle symbolic name and location in
StateReader.readBundleDescription:

result.setSymbolicName(readString(in, true));
result.setLocation(readString(in, true));

This saves about 2MB in heap space when running a large Eclipse-based product
with > 1000 plugins.
Comment 1 John Arthorne CLA 2005-04-05 17:39:10 EDT 
Note: we don't need to think about this until after shipping 3.1.  I just wanted
to make a note to investigate for the next maintenance branch release.
Comment 2 John Arthorne CLA 2005-09-28 10:14:26 EDT 
I think this can be closed because no more 3.0.x maintenance releases are planned.
Comment 3 Thomas Watson CLA 2005-09-28 10:18:18 EDT 
closing as wontfix per comment 2