Bug 256820

Summary:	[fwAdmin] Optimize SimpleConfiguratorManipulators use of BundleState.resolve
Product:	[Eclipse Project] Equinox	Reporter:	Simon Kaegi <simon_kaegi>
Component:	p2	Assignee:	P2 Inbox <equinox.p2-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	Ed.Merks, pascal
Version:	3.5	Keywords:	performance
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Simon Kaegi

2008-11-27 13:16:21 EST

We resolve our state a number of times in SimpleConfiguratorManipulator and this call is very expensive. It looks like for the typical case we can optimize what we're resolving when saving to a smaller set of bundles (just those required for resolving the bundles on osgi.bundles)and when updating the manipulator's set of bundles possibly avoiding resolving altogerther.

Comment 1 Pascal Rapicault

2009-01-07 21:59:39 EST

Given all of our efforts around reading and writing fwk admin only once. I will remove this from 3.5. We have more important things to address.

Comment 2 Eclipse Webmaster

2019-09-06 16:12:46 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 3 Ed Merks

2020-02-20 05:47:09 EST

I assume this issue is stale and/or has already been addressed.