Community
Participate
Working Groups
Running with a p2-enabled SDK, I'm seeing these messages in my console during startup: Time Fetching Metadata Site http://download.eclipse.org/tools/mylyn/update/e3.4/site.xml was: 3375 ms Time Fetching Metadata Site http://capilano.ottawa.ibm.com/ganymede/site.xml was: 1328 ms It looks like we're eagerly hitting servers on startup, which we must avoid unless absolutely necessary. In my case I have no dropins folder at all, so I don't see why we should need to do anything during startup. Even if there is a dropins folder, I would only expect to be hitting repositories if the dropins folder contents have changed and install/uninstall operations are needed.
John would it be possible that the update checker would trigger this?
If the auto-update preference is set for startup, this would definitely happen.
Ok, I suggest for auto-update checking we schedule this to run after some delay on startup to avoid slowing down other initialization work. As an end user this is not a critical thing that needs to happen right away. Something like a 30-60s delay would do it. I'll do some more careful profiling once we have a working p2ized SDK to see what else is going on during startup.
If the user has selected "check on startup" this happens...otherwise on startup a delay is computed so that it meets the specified schedule. Note the timing is the same as UM did it. I'll await your profiling before making any changes/introducing a delay.
Has any investigation done on this?
No further investigation has been done. I'll assign it to myself so I don't lose track of it.
see also bug #227582
There are no concrete problems at the moment so clearing milestone. Some profiling would be useful time permitting.
*** This bug has been marked as a duplicate of bug 230340 ***
