Community
Participate
Working Groups
Created attachment 106513 [details] patch While profiling for bug 238312 I noticed that getEclipseRealLocation is doing some unnecessary work. We try interpreting an incoming location string as an URL which is not really necessary in this case. This unfortunately triggers the URL parsing code which can be expensive. A far simpler check will suffice. This might normally not be a big deal however in larger installs the number of calls to getEclipseRealLocation grows faster than linearly because of the way we check bundle locations. The attached fix does not attempt to alter the overall algorithm but nonetheless removing the URL parsing step has a noticeable impact on installs with >500 bundles. Starting from a 3.4 SDK and adding 500 dummy bundles: savings approx. 1 sec Starting from a 3.4 SDK and adding 4000 dummy bundles: savings approx. 100 sec
I've committed to the 3.5 stream to allow further testing.
Marking fixed along with bug 238312