Bug 89988 - [osgi] accessing bundledata file from a remote install
Summary: [osgi] accessing bundledata file from a remote install
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2005-04-01 11:45 EST by Pascal Rapicault CLA
Modified: 2007-03-27 16:36 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Rapicault CLA 2005-04-01 11:45:54 EST
The bundle data is cached in the configuration area.
In case of remote shared install, accessing it can be costly.

First we need to verify that it is actually costly, if so we need to come up
with a scheme to fix that. For example we could have a local copy of the file.
Comment 1 Thomas Watson CLA 2005-04-01 12:04:11 EST
If access to the bundledata in the shared install is costly then we have other 
issues.  Would this not mean that access to the binary bundles in the shared 
install would also be costly?  The bundledata is a relatively small file 
(compared to the rest of the shared binaries) and is only read once at startup.

If remote access is slow then we should consider how one would create a local 
copy of everything from a remote install.  Or simply do not suggest remote 
installs unless your access is fast.
Comment 2 Pascal Rapicault CLA 2005-04-01 12:14:41 EST
I think that what I meant was .lazydata file.
Comment 3 Jeff McAffer CLA 2005-04-02 22:12:28 EST
all the bundles etc might be remove (in the shared install) but if we are 
repeately going to the cache for stuff and the cache is in some shared spot, 
there may be some issues.  It would be interesting to know if there are options 
for putting the caches locally.
Comment 4 Thomas Watson CLA 2007-03-27 16:36:38 EDT
We do not plan to fix this.