| Starting Galileo takes a while... [message #351817] |
Tue, 28 July 2009 05:57  |
Eclipse User |
|
|
|
Galileo startup takes pretty long (I would say about a minute on my machine). And only during the last 10 or so seconds one gets the progress bar at the bottom of the splashscreen, which is then of course finished pretty quickly, but since it appears so late I find it only marginally useful. With Ganymede it appeared much earlier (and overall I am pretty sure, the startup took a bit shorter).
Just out of curiosity: what is eclipse doing so long during program start? Are there so many pre-loaded classes or packages? And why is the progressbar only appearing so late?
I have installed the J2EE version, in case that matters.
Michael
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Starting Galileo takes a while... [message #485473 is a reply to message #485336] |
Fri, 11 September 2009 17:12  |
| Eclipse User |
|
|
|
On 9/11/09 8:26 AM, Michael Moser wrote:
> Name wrote:
>> Michael Moser a écrit :
>>> Galileo startup takes pretty long (I would say about a minute on my
>>> machine). And only during the last 10 or so seconds one gets the
>>> progress bar at the bottom of the splashscreen, which is then of
>>> course finished pretty quickly, but since it appears so late I find
>>> it only marginally useful. With Ganymede it appeared much earlier
>>> (and overall I am pretty sure, the startup took a bit shorter).
>>>
>>> Just out of curiosity: what is eclipse doing so long during program
>>> start? Are there so many pre-loaded classes or packages? And why is
>>> the progressbar only appearing so late?
>>>
>>> I have installed the J2EE version, in case that matters.
>>
>> Could you have the "-clean" command line option ? This option might
>> not be included in the progress bar...
>
> Yes, I have the -clean option set. Without it I had too much trouble (constantly seeing old states) when developing plugins...
You should definitely try removing -clean to see if startup time
improves; last time I discussed it with those who know, that option
forces p2 to do a lot of work during startup.
Any problems you have during plug-in development should not be related
to -clean since plug-ins are tested in a separate instance of Eclipse,
not the one that your developing in.
Hope this helps,
Eric
|
|
|
| Re: Starting Galileo takes a while... [message #485575 is a reply to message #485473] |
Sun, 13 September 2009 16:20 |
| Eclipse User |
|
|
|
Eric Rizzo wrote:
>> ...
> You should definitely try removing -clean to see if startup time
> improves; last time I discussed it with those who know, that option
> forces p2 to do a lot of work during startup.
Wow - you are right! The startup time is dramatically shorter. All complaints wiped away. In contrast: I'm impressed! :-)
> Any problems you have during plug-in development should not be related
> to -clean since plug-ins are tested in a separate instance of Eclipse,
> not the one that your developing in.
I know. "Plugin-development" was the wrong term. Enabling/disabling of (different - sometimes colliding - versions of) plugins would have been more precise. Before the Ganymede version I had activated/deactivated different eclipse plugins not by using Eclipse's configuration manager but by moving .link files in and out of the links folder. And that often heavily interfered with the built-in config mgmt. unless one specified the -clean option.
But the links mechanism doesn't seem to work any more anyway (at least not as expected) and so I had switched to the "official" way to manage plugins in the last version. So I can now also remove that relict. Very good!
Cheers and thanks,
Michael
|
|
|
Powered by
FUDForum. Page generated in 0.04636 seconds
Home